Help recovering cluster
Hello all, New to the group, apologies for any poor information. I have a home lab with a single host ovirt setup. I actually don't think I ever set it up exactly right, the agent vm was never created, it was running on the host server. But it ran and I had a handful of vm's running on it successfully. I knew I had to rebuild it but was waiting for funds for extra hardware. Then the other day I came home and could no longer access the web portal. Could get to the login page but after entering my auth info it just hangs. I'm honestly not even sure where to start. Does anyone know any good troubleshooting docs? Or any idea what may be happening? I can see the VM images and such in the proper folders so I don't think I have .lost anything. But can't access any of the vm's now. Any help would be appreciated. Joe
On March 8, 2020 5:34:30 PM GMT+02:00, Joe Sherman <joesherman1979@gmail.com> wrote:
Hello all,
New to the group, apologies for any poor information. I have a home lab with a single host ovirt setup. I actually don't think I ever set it up exactly right, the agent vm was never created, it was running on the host server. But it ran and I had a handful of vm's running on it successfully. I knew I had to rebuild it but was waiting for funds for extra hardware. Then the other day I came home and could no longer access the web portal. Could get to the login page but after entering my auth info it just hangs. I'm honestly not even sure where to start. Does anyone know any good troubleshooting docs? Or any idea what may be happening? I can see the VM images and such in the proper folders so I don't think I have .lost anything. But can't access any of the vm's now. Any help would be appreciated.
Joe
Hey Joe, Welcome to the mailing list. As you don't use the hosted infrastucture , you will need to sort some stuff for yourself. First step, check if the HostedEngine VM is alive - use ping and then try with ssh. If you manage to get in -> restart the 'ovirt-engine.service'. Wait 30-40s and try to access the web UI. Otherwise, you can reboot the whole VM and check what is going on. Best Regards, Strahil Nikolov
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.
On March 8, 2020 9:47:10 PM GMT+02:00, joesherman1979@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@ovirt.org To unsubscribe send an email to users-leave@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/WOXXJMJPA5GCUZ...
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
Sorry about the email include. I'll do my best to leave it out from now on. If they are just normal disks then o really should just be able to transport them to another kvm machine, import the disks into a VM and use them, right?
On March 9, 2020 12:49:55 AM GMT+02:00, joesherman1979@gmail.com wrote:
Sorry about the email include. I'll do my best to leave it out from now on.
If they are just normal disks then o really should just be able to transport them to another kvm machine, import the disks into a VM and use them, right? _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/7PYEZKMROMGBO2...
Yes, But you need the VM's definition (the xml that is visible in the vdsm.log during power up), or you will have to create it manually. Actually, oVirt is the management part with KVM /we should not forget qemu/ for hypervisor. You do not need to move them - just define the VMs via virsh and you are good to go. Best Regards, Strahil Nikolov
participants (3)
-
Joe Sherman -
joesherman1979＠gmail.com
-
Strahil Nikolov