Hi , Without the engine - this will be hard.The engine knows the configuration and the disks of each VM so the Hypervisor can start it. In your case I would focus on the engine as this could be (or not) the easier approach.
Otherwise you need to run qemu-img against each image (just an uuid, no meta or lease ) , find your image and copy it to a standalone KVM. Once you have the disk, you should try to recall what was the host CPU type (should be the same on the whole cluster) and create a new VM using a COPY of your image . If KVM manages to start and the machine boots - you are done. As you can see , fixing the engine might be easier - especially with the help of the community. Best Regards, Strahil NikolovOn Mar 20, 2019 18:01, siove...@gmail.com wrote: > > Hi, I had problems with my ovirt-engine and it does not raise. I have some > virtual machines in an NFS domain that is located in one of the nodes and I > want to get one of the virtual machines. The problem is that what appears is > a series of identifiers (ID) and I don't know what the virtual machine is, > because by name I can not find it. There are some .meta files where I can see > the Description of some Virtual Machines. Please I need help > _______________________________________________ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/NXNAZBOSGTIRCGLT2WCW7DMOMOXQZ3G6/ _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VWIIPBUMZ7WZUCXEZFV3UVQPCA5MDVRO/
