Long shot on VM failing to start
We are moving to an oVirt 4.4.9 environment from a 4.3.4.3 environment and have run into a major issue. The method for migration to the new system is to shutdown a VM on the old system, build a new VM on the new system with the same IP/name etc. This has worked for several VMs so far but the latest new build failed and we had to roll back - i.e. start the old VM. The old VM fails to start with the following message in the VMs libvirt qemu log: libvirtd quit during handshake: Input/output error shutting down, reason=failed Any ideas? Regards Simon...
On Wed, Mar 09, 2022 at 12:07:51AM -0000, simon@justconnect.ie wrote:
We are moving to an oVirt 4.4.9 environment from a 4.3.4.3 environment and have run into a major issue. The method for migration to the new system is to shutdown a VM on the old system, build a new VM on the new system with the same IP/name etc.
This seems unnecessarily elaborate. Was the method choice deliberate? Why not migrate the storage domains or update the clusters?
This has worked for several VMs so far but the latest new build failed and we had to roll back - i.e. start the old VM. The old VM fails to start with the following message in the VMs libvirt qemu log:
libvirtd quit during handshake: Input/output error shutting down, reason=failed
This is not too informative but it seems to me that something breaks when trying to start qemu process. Could you check journal for libvirtd if there are any errors? Also please check journal for vdsm and make sure the service did not restart. Hope this helps, Tomas
Any ideas? Regards Simon... _______________________________________________ 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/4XOQCOLVNTOL2R...
-- Tomáš Golembiovský <tgolembi@redhat.com>
Thanks Tomas, The method choice was decided based on a few factors. 1. The environment is a Production Live environment which, through neglect, has been over utilised. 2. The stability of the cluster has been an issue which has resulted in several new clusters being built. 3. Zero or near to Zero downtime is a priority. 4. Lack of confidence in oVirt from certain quarters. Further investigation revealed a systemd-machined.service failure on all 3 nodes in the cluster. The service will not start without a reboot, which is a non runner at this time. A decision has been made to export and import the VMs to the new environments to avoid possibly extended outage periods. Regards Simon...
WARNING: The restore from 4.3 to 4.4 works only if it was taken from 4.3.10 Update before taking the backup ! Best Regards,Strahil Nikolov Thanks Tomas, The method choice was decided based on a few factors. 1. The environment is a Production Live environment which, through neglect, has been over utilised. 2. The stability of the cluster has been an issue which has resulted in several new clusters being built. 3. Zero or near to Zero downtime is a priority. 4. Lack of confidence in oVirt from certain quarters. Further investigation revealed a systemd-machined.service failure on all 3 nodes in the cluster. The service will not start without a reboot, which is a non runner at this time. A decision has been made to export and import the VMs to the new environments to avoid possibly extended outage periods. Regards Simon... _______________________________________________ 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/7GGC36GIOWXL5I...
participants (3)
-
simon＠justconnect.ie -
Strahil Nikolov -
Tomáš Golembiovský