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.
(In reply to Eduardo Habkost from comment #0)
> Steps to Reproduce:
> 1. Source: /usr/libexec/qemu-kvm -m 1024 -drive
> file=/var/lib/libvirt/images/rhel64.qcow2,format=qcow2 -vnc :0 -vga cirrus
> -nodefaults -monitor stdio
> 2. Destination: /usr/libexec/qemu-kvm -m 1024 -drive
> file=/var/lib/libvirt/images/rhel64.qcow2,format=qcow2 -vnc :0 -vga cirrus
> -nodefaults -monitor stdio -incoming tcp:0.0.0.0:1234
> 3. Monitor on source: migrate tcp:destination-host:1234
Oops, I forgot to add the machine-type. But the bug can be reproduced when using "-machine rhel6.4.0" as well.
From hw/acpi/piix4.c:
/* qemu-kvm 1.2 uses version 3 but advertised as 2
* To support incoming qemu-kvm 1.2 migration, change version_id
* and minimum_version_id to 2 below (which breaks migration from
* qemu 1.2).
*
*/
static const VMStateDescription vmstate_acpi = {
.name = "piix4_pm",
.version_id = 3,
.minimum_version_id = 3,
.minimum_version_id_old = 1,
.load_state_old = acpi_load_old,
The v3 format of qemu-0.13 (implemented by commit 4cf3e6f3d85492f20a773dd6c9068ab89ba24a18) is not compatible with the v3 format of qemu-0.15 and newer (broken by commit 23910d3f669d46073b403876e30a7314599633af). RHEL-6 is using the v3 format that was included on qemu-0.13, which is not compatible with qemu 0.15 and newer (including qemu 1.2).
Probably setting minimum_version_id=2 will work.
Comment 5Miroslav Rezanina
2013-10-31 07:56:06 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.