Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1016736 - CPU migration data has version_id 12 but version 11 format
CPU migration data has version_id 12 but version 11 format
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm (Show other bugs)
6.6
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Eduardo Habkost
Virtualization Bugs
: Reopened
Depends On:
Blocks: 889670 915399 1004743
  Show dependency treegraph
 
Reported: 2013-10-08 11:17 EDT by Eduardo Habkost
Modified: 2013-12-06 11:46 EST (History)
13 users (show)

See Also:
Fixed In Version: qemu-kvm-0.12.1.2-2.414.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1004743
Environment:
Last Closed: 2013-11-21 01:03:59 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:1553 normal SHIPPED_LIVE Important: qemu-kvm security, bug fix, and enhancement update 2013-11-20 16:40:29 EST

  None (edit)
Comment 3 Qunfang Zhang 2013-10-15 02:49:23 EDT
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 03:57:56 EDT
Fix included in qemu-kvm-0.12.1.2-2.414.el6
Comment 7 Qunfang Zhang 2013-10-17 02:31:45 EDT
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 10:58:50 EDT
(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 02:13:13 EDT
Okay, thanks for the valuable suggestions.
Comment 11 Qunfang Zhang 2013-10-28 02:03:49 EDT
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 01:03:59 EST
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.