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.
Bug 1004743 - XSAVE migration format not compatible between RHEL6 and RHEL7
Summary: XSAVE migration format not compatible between RHEL6 and RHEL7
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Eduardo Habkost
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1016736
Blocks: 889670 915399
TreeView+ depends on / blocked
 
Reported: 2013-09-05 11:50 UTC by Paolo Bonzini
Modified: 2014-06-18 03:35 UTC (History)
9 users (show)

Fixed In Version: qemu-kvm-1.5.3-11.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1004773 1016736 (view as bug list)
Environment:
Last Closed: 2014-06-13 09:36:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Paolo Bonzini 2013-09-05 11:50:57 UTC
VMState format for XSAVE data is incompatible between RHEL6 and RHEL7.

RHEL6 used a subsection, RHEL7 bumped the version number.  As a result, SandyBridge, Haswell, Opteron_G4 and Opteron_G5 CPU models cannot be migrated to RHEL7.

Comment 2 Paolo Bonzini 2013-09-06 15:19:04 UTC
*** Bug 997702 has been marked as a duplicate of this bug. ***

Comment 3 huiqingding 2013-09-11 02:04:29 UTC
I duplicate this bug to bug 997702, as talked to Paolo:

https://bugzilla.redhat.com/show_bug.cgi?id=997702#c11

*** This bug has been marked as a duplicate of bug 997702 ***

Comment 4 Paolo Bonzini 2013-10-10 09:44:08 UTC
This affects all models, not just those listed.

Comment 5 Eduardo Habkost 2013-10-17 14:44:00 UTC
(In reply to Paolo Bonzini from comment #4)
> This affects all models, not just those listed.

Does it? If xsave is not enabled on CPUID, the xsave section will be skipped.

Comment 7 Paolo Bonzini 2013-10-18 07:20:48 UTC
See bug 1016736 comment 4.  But it is possible that for non-XSAVE models the problem is the ACPI one.

Comment 8 Miroslav Rezanina 2013-10-31 07:56:21 UTC
Fix included in qemu-kvm-1.5.3-11.el7

Comment 10 FuXiangChun 2013-11-11 08:10:12 UTC
Verify this bug with qemu-kvm-1.5.3-18.el7.x86_64.rpm

Testd four cpu model(include xsave flag)
1. Opteron_G5 2. Opteron_G4 3. Hasswell 4. SandyBridge

Tested seven cpu models(not include xsave flag)

AMD cpu model: Opteron_G1,Opteron_G2 and Opteron_G3
Intel cpu model:Westmere,Nehalem,Penryn and Conroe

All cpu model above works well when migrating from rhel6.5 to rhel7.0 host.


Base on this result above. This bug is fixed.

Comment 12 Ludek Smid 2014-06-13 09:36:33 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.


Note You need to log in before you can comment on or make changes to this bug.