Thanks for the reply.
I ended up moving the disk for another VM that was also paused and using the same NFS share for storage. I moved the disk to a different share, and then moved it back. Then to my surprise, the VM would start up. I then tried to start the VM this thread opened on and it also started up. So this appears to be due to some transient network error not being able to access the NFS share the VM was stored on. I am not sure what sort of checks Ovirt does to determine of the share is accessible, but we have seen this before with our OVIRT setup. Rebooting switches for maintenance for example would pause VMs in our setup. Rebooting the manager server after the network is stabilized seems to fix everything. I looked through the network logs to see what would have caused this but didn’t see any issue with the devices hosting this NFS share. So couldn’t be sure what caused this. It seems OVIRT is very intolerant of ANY network issues whatsoever, even ones designed to improve network stability and availability (spanning tree, failover mechanisms, etc.). In the event of a network situation, why wouldn’t OVIRT try accessing the share again once the network was stabilized. Perhaps this is simply due to poor design of our particular OVIRT installation, but it seems really finicky with ANYTHING changing on the network. If we were to design this again, I wouldn’t rely on any network storage to run VMs and put everything on gluster mounts local to the hosts. would appreciate any ideas on why this might have happened.
Thanks for the reply. I’ll keep this link handy for the future on running VMs via command line. Thanks.
Bob
From: marcel@deheureu.se (marcel d'heureuse) <marcel@deheureu.se>
Sent: Thursday, September 9, 2021 4:49 PM
To: bob.franzke@mdaemon.com; users@ovirt.org
Subject: Re: [ovirt-users] Re: Cannot Start VM After Pausing due to Storage I/O Error
Moin,
Normally you can use virsh to start vm which are in pause.
https://www.google.com/amp/s/www.cyberciti.biz/faq/linux-list-a-kvm-vm-guest-using-virsh-command/
You have to use saslpasswd2 -a libvirt username to get access on comandline.
It is importand that you Resum that vm on the same host where it was paused.
Good luck...
Br
Marcel
Am 9. September 2021 22:10:52 MESZ schrieb "bob.franzke--- via Users" <users@ovirt.org>:
OK looking into this further, it seems that I was incorrect about the Gluster situation on these hosts. There are three hosts which form a replicated arbitrated gluster volume between them. There is a second gluster volume which is distributed but only seems to exist on the 4 host (the one the failed VMs are running on. I am not sure why this was set up this way.
After all that I looked closer and realized there is an NFS share which these VMs disks are located on. I can access and write to this NFS share from the host itself so I am not sure what the story is as to why I cannot get this VM to come up. Seems like everything is there for it to do so. The error I get when trying to start up the VM is the following:
<vm-name> has been paused due to storage I/O problem.
How can I determine what this I/O problem actually is? IS the disk file corrupted somehow? Both VMs that won;t start are using this NFS share. Others that are running also use it so I am ot sure what the problem here is or where to start looking for an answer. Thanks in advance for your help.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/EX7TAYPEKKVEXQ275UNRRA473CBHB6JI/