OLVM : Live Migration of VM Fails With Error "Migration failed due to an Error: Fatal error during migration".
(Doc ID 3047497.1)
Last updated on SEPTEMBER 26, 2024
Applies to:
Linux OS - Version Oracle Linux 8.8 with Unbreakable Enterprise Kernel [5.4.17] and laterx86_64
Symptoms
Live migration of a VM fails with the following error in the engine.log.
2024-09-12 12:27:24,377+08 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-27) [35ad8e9e] EVENT_ID: VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed due to an Error: Fatal error during migration VM: <vm-name>, Source: <source-host-name>, Destination: <destination-host-name>. 2024-09-12 12:27:24,377+08ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-27) [35ad8e9e] EVENT_ID: VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed due to an Error: Fatal error during migration VM: <vm-name>, Source: <source-host-name>, Destination: <destination-host-name>.
Destination host reports the following error in the vdsm.log.
2024-09-12 12:27:23,330+0800 ERROR (migsrc/51701d10) [virt.vm] (vmId='xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx') Cannot check QEMU binary /usr/bin/qemu-system-x86_64: No such file or directory (migration:331) 2024-09-12 12:27:24,345+0800 INFO (migsrc/51701d10) [virt.vm] (vmId='xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx') Switching from State.STARTED to State.FAILED (migration:229)
Changes
The destination host is a newly added host to the cluster with latest version of packages.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |