Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Using RHEVM and VDSM I have cluster with 2 hosts, one have VDSM 3.1 and the second have VDSM 3.2.
My VM is running under 3.1 host and when I'm trying to migrate the VM it fails: (from qemu logs)
qemu: warning: error while loading state for instance 0x0 of device 'ram'
load of migration failed
2013-03-19 01:39:19.083+0000: shutting down
Tried to migrae using virsh and got the same error
virsh migrate --live <vm_name> qemu+ssh://<hostname>/system
dumpxml from 3.1 host and virsh create using the xml on 3.2 host successfully created.
Version-Release number of selected component (if applicable):
host 3.1 - vdsm-4.10.2-1.8.el6ev.x86_64, qemu-kvm-rhev-0.12.1.2-2.348.el6.x86_64, libvirt-0.10.2-18.el6.x86_64
host 3.2 - vdsm-4.10.2-11.0.el6ev.x86_64, qemu-kvm-rhev-0.12.1.2-2.355.el6_4.2.x86_64, libvirt-0.10.2-18.el6.x86_64
Steps to Reproduce:
1.On RHEVM webadmin create datacenter 3.0 and cluster 3.1
2.Add 2 hosts to the cluster (host 3.1 vdsm and host 3.2 vdsm)
3.Create VM and run it on host 3.1 vdsm
4.Migrate the VM to host 3.2 vdsm
Actual results:
VM migration failed
Expected results:
VM migration should succeed.
(In reply to comment #0)
> Version-Release number of selected component (if applicable):
> host 3.1 - vdsm-4.10.2-1.8.el6ev.x86_64,
> qemu-kvm-rhev-0.12.1.2-2.348.el6.x86_64, libvirt-0.10.2-18.el6.x86_64
> host 3.2 - vdsm-4.10.2-11.0.el6ev.x86_64,
> qemu-kvm-rhev-0.12.1.2-2.355.el6_4.2.x86_64, libvirt-0.10.2-18.el6.x86_64
qemu-kvh build 348 was never intended for production use and is an intermediary build, used during development.
This is a recurrent problem: it appears there's a VDSM image being used for testing with this version of qemu. If that's the case, please make sure the tests stop, as they're not valid at all.