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 1016736 - CPU migration data has version_id 12 but version 11 format
Summary: CPU migration data has version_id 12 but version 11 format
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Eduardo Habkost
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 889670 915399 1004743
TreeView+ depends on / blocked
 
Reported: 2013-10-08 15:17 UTC by Eduardo Habkost
Modified: 2013-12-06 16:46 UTC (History)
13 users (show)

Fixed In Version: qemu-kvm-0.12.1.2-2.414.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 1004743
Environment:
Last Closed: 2013-11-21 06:03:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:1553 0 normal SHIPPED_LIVE Important: qemu-kvm security, bug fix, and enhancement update 2013-11-20 21:40:29 UTC

Comment 3 Qunfang Zhang 2013-10-15 06:49:23 UTC 
Hi, Eduardo

We plan to run a round of stable guest abi test on RHEL6.5 host after this bug is fixed (no rhel7 involved, juzhang will arrange the rhel7 test). So I want to confirm with you for the following stuff:

(1) Do we need to test both AMD and Intel host? 
(2) Does the guest os type matter? Could we only run with windows guest? Because we ran RHEL guest before and we need to run windows guest this time for the planning test coverage matrix. If rhel guest is needed, please tell me.

Thanks,
Qunfang
Comment 5 Miroslav Rezanina 2013-10-16 07:57:56 UTC 
Fix included in qemu-kvm-0.12.1.2-2.414.el6
Comment 7 Qunfang Zhang 2013-10-17 06:31:45 UTC 
Hi, Eduardo

Could you help check my comment 3? Because we have only one week to verify the bugs in errata, so we need to your help to estimate the test scope to avoid we are testing too many configuration and the time is not enough.

Thanks,
Qunfang
Comment 8 Eduardo Habkost 2013-10-17 14:58:50 UTC 
(In reply to Qunfang Zhang from comment #3)
> Hi, Eduardo
> 
> We plan to run a round of stable guest abi test on RHEL6.5 host after this
> bug is fixed (no rhel7 involved, juzhang will arrange the rhel7 test). So I
> want to confirm with you for the following stuff:
> 
> (1) Do we need to test both AMD and Intel host? 

Yes, please. On each vendor, please test at least one model supporting xsave, and at least one model not supporting xsave.

> (2) Does the guest os type matter? Could we only run with windows guest?
> Because we ran RHEL guest before and we need to run windows guest this time
> for the planning test coverage matrix. If rhel guest is needed, please tell
> me.

The guest OS shouldn't matter, but some guests may make bugs more visible (e.g. I know Linux can use xsave. I don't know about Windows). It would be interesting to use guest-side software that actually uses xsave and run it while migrating (if you happen to already have a guest-side test case for xsave). On the other hand, considering that xsave migration was already working and the new code didn't touch the xsave section, testing using Windows guests should suffice if you are really short of time/resources.
Comment 9 Qunfang Zhang 2013-10-18 06:13:13 UTC 
Okay, thanks for the valuable suggestions.
Comment 11 Qunfang Zhang 2013-10-28 06:03:49 UTC 
The bug following bug is verified pass on qemu-kvm-415, so I would like to verified this bug now. QE will continue test a round of stable guest abi test for sanity.

Bug 1022821  - live-migration from RHEL6.5 to RHEL6.4.z fails with "error while loading state for instance 0x0 of device 'cpu'"
Comment 13 errata-xmlrpc 2013-11-21 06:03:59 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.