On Tue, Dec 21, 2021 at 8:16 AM richmoch--- via Users <users@ovirt.org> wrote:
Hi *,
I am having a problem where on a KVM host I run virsh list --all. I only see the running VMs :
[root@MBGVRT3323 ~]# virsh list --all Please enter your authentication name: Please enter your password: Id Name State ----------------------------------- 3 MBPDBS0583U-CLONE running 4 MBGDBS3156U-CLONE running
I know there are two more VMs that are shutdown , and if I run virsh list --state-shutoff , nothing is returned. in fact, look at the numbering of the two running VMs, 3 and 4. The GUI shows the two running and the other two as being shutdown.
Why is this happening ? Given this, seems the only way to start the two VMs which are down is in the GUI and not with virsh start domain which seems limiting. Any ideads would be greatly appreciated.
You got it accurately. In oVirt, using libvirt terminology, VMs are transient. You can't (easily, robustly) start a VM if the engine is down. If the engine is up and functioning, you can also use the API, one of the SDKs, or ansible, to start VMs. So if in "seems limiting" you refer to using the GUI, you have other options. But if you refer to "engine must be up", then this is indeed a limitation. Engine must be up, and you are supposed to take frequent backups of it (using engine-backup) in case it's gone/corrupted/whatever and you need to restore. If it's gone and you have no backup, you can set up a new engine, and import the storage domains. Best regards, -- Didi