[ovirt-users] Re: Help recovering cluster
On March 8, 2020 9:47:10 PM GMT+02:00, joesherman1979(a)gmail.com wrote:
Thank you for the reply. When it was first setup I messed up and
didn't
create the HostedEngine VM. Instead the engine is installed on the
host. This is wrong, I know, but it had worked for a while. Now it is
not. At this point if I could figure out how to load the images in a
straight KVM setup I would be ok. But I don't understand the drive
image format. I believe I have found the drive images but the file
names are just guids. Is this just standard img format with no file
extension? Can I just load these files as disk images in KVM? I am
working on backing it all up now so I can begin to try things.
I did check and the ovirt-engine service is started on the host without
error.
BTW. This is on centos 7.
Thank you for any help you have.
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WOXXJMJPA5G...
As the HostedEngine has a internal database and oVirt was planned to support thousands of
VMs , the only way to have unique names is via the uids.
They are just simple KVM disks.
You can always run 'qemu-img info <long uid> to get information about the disk.
If you want to control the VMs without the engine (as it currently doesn't work
peoperly).
You need to:
1. Find the VM's xml in the vdsm.log and save it in a separate file
2. Define this alias on the host:
alias virsh='virsh -c
qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf'
3. Define the VM via:
virsh define <file_from_step1>
4. Try to start the VM:
virsh start VM
Keep in mind that you might need to :
A) create symbolic links for the storage domains (this is specific to storage type and
your custom installation) - the error will be in the libvirt log
B) define the ovirtmgmt or another network.
P.S.: It will be nice if you leave aome old e-mails in your reply, as it isbhard tracking
what was already discussed or what was refferenced before.
Best Regards,
Strahil Nikolov