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.
Possibly caused by the fix for bug 903123. The fix for bug 903123 prevents 6.5->5.4.z live migration if the steal time MSR is being set by the guest.
Please check if the bug is reproducible when running Windows as guest, and when using RHEL6.3 as guest.
Here is an update:
Use rhel6.5 as guest:
qemu-kvm-407 --> qemu-kvm-0.12.1.2-2.355.el6_4.9 Failed
qemu-kvm-402 --> qemu-kvm-0.12.1.2-2.355.el6_4.9 Succeeded
Hi, PM and Ademar
Could you give a help to ack this? We need this fix as the bug is a regression and a common scenario in RHEL6.5. QE hopes to receive the official build asap and need to arrange another round of function test for it that will take at least 1 week.
Thanks,
Qunfang
Reproduced and verified this issue again.
Steps to Reproduce:
1. install RHEL6.5 to host A
2. install RHEL6.4GA to host B, upgrade with latest Z stream qemu-kvm and kernel
3. migrate from A to B
With qemu-kvm-414, migration failed on:
(qemu) qemu: warning: error while loading state for instance 0x0 of device 'cpu'
load of migration failed
With qemu-kvm-415, migration succeeded without no error.
CLI:
/usr/libexec/qemu-kvm -name test -M rhel6.4.0 -S -enable-kvm -m 4096 -smp 2,sockets=2,cores=1,threads=1 -nodefaults -monitor stdio -boot menu=on -rtc base=utc,clock=host,driftfix=slew -drive file=/mnt/rhel6.5.qcow2,if=none,id=drive-virtio-disk1,format=qcow2,cache=none,werror=stop,rerror=stop,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,drive=drive-virtio-disk1,id=virtio-disk1,bootindex=1 -k en-us -vga qxl -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=67108864 -spice port=5900,disable-ticketing,seamless-migration=on
As per above, this issue has been fixed.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2013-1553.html