Incidentally, I also did find this in the OVIRT logs:

MainProcess|jsonrpc/7::DEBUG::2021-09-09 15:36:32,791::commands::219::root::(execCmd) FAILED: <err> = 'mount.nfs: No route to host\n'; <rc> = 32

MainProcess|jsonrpc/7::DEBUG::2021-09-09 15:36:32,792::logutils::319::root::(_report_stats) ThreadedHandler is ok in the last 125 seconds (max pending: 0)

MainProcess|jsonrpc/7::ERROR::2021-09-09 15:36:32,793::supervdsm_server::103::SuperVdsm.ServerCallback::(wrapper) Error in mount

Not sure what it means. ‘No route to host’ is not accurate as the host the NFS  mount is hosted on was completely accessible from a network perspective. Not sure if this is relevant or not, but thought I would include it.

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/