with oVirt, the virtual machines that does not run are not present on the
node. You have the storage where are the virtual machines stored. You also
have the engine which stores every virtual machine in its database. It also
knows where the machine should run. This is why you can see the
it might happen you are solving the same issue as is discussed within this
thread: "[ovirt-users] Windows vm and cpu type"
Maybe you do not have all flags turned on in the bios?
On Tue, Aug 28, 2018 at 5:13 PM carl langlois
> Why when en try to do a Windows
> Ok I see. Many thanks.
> *De: *"Petr Kotas"
> *Para: *supo...@logicworks.pt
> *Cc: *"users"
> *Enviadas: *Segunda-feira, 30 De Julho de 2018 7:26:30
> *Assunto: *Re: [ovirt-users] Pool
yes it is possible, unless you enabled `Delete protection` checkbox while
creating the pool.
Then just detach the VM from the pool and delete it afterwards.
On Sun, Jul 29, 2018 at 7:31 PM wrote:
> I create a pool with
you should be fine. It will be handled either by scheduler or by pinning to
you gpu node.
On Tue, Jul 24, 2018 at 6:43 AM femi adegoke
> Planning to build a hyperconverged 3 host w HE oVirt cluster + Gluster.
> Is it ok if only one of the hosts has a GPU?
would you mind being more specific with your question?
What are you trying to achieve?
On 16.7.2018 17:42, Николаев Алексей wrote:
What are best practices to run docker images into oVirt infra: core os
or something else?
I have never done anything more then install the guest agent and it worked.
On 18.7.2018 08:41, Hari Prasanth Loganathan wrote:
A Quick question,
As per this document
> On Thu, Feb 8, 2018 at 2:51 PM, Petr Kotas <pko...@redhat.com> wrote:
>> Hi Maoz,
>> it looks like cannot connect due to wrong setup of ssh keys. Which linux
>> are you using?
>> The guide for setting the ssh connection to libvi
it looks like cannot connect due to wrong setup of ssh keys. Which linux
are you using?
The guide for setting the ssh connection to libvirt is here:
May it helps?
On Wed, Feb 7, 2018 at 10:53 PM, maoz zadok wrote:
have you tried it on other linux distributions? Scientific is not
My guess based on your log is there are somewhere missing certificates,
maybe different path?.
You can check the paths by the documentation:
> At 2018-02-05 20:52:04, "Petr Kotas" <pko...@redhat.com> wrote:
> I have experimented on the issue and figured out the reason for the
> original issue.
> You are right, that the vm1 is not properly stopped. This is due to
can you please send a vdsm logs? The 4.2 release added the little different
deployment from the engine.
Now the ansible is also called. Although I am not sure if this is your case.
I would go for entirely removing the vdsm and installing it from scratch if
it is possible for you.
I have experimented on the issue and figured out the reason for the
You are right, that the vm1 is not properly stopped. This is due to the
known issue in the graceful shutdown introduced in the ovirt 4.2.
The vm on the host in shutdown are killed, but are not marked as
There are some scattered on the internet. Are You looking for something
specific? Maybe we can come up with something.
On Tue, Aug 22, 2017 at 10:52 AM, wrote:
> Are there any other resources, blogs or install videos similar to this?
> (see link)
Mail list logo