Bug 1022821

Summary: live-migration from RHEL6.5 to RHEL6.4.z fails with "error while loading state for instance 0x0 of device 'cpu'"
Product: Red Hat Enterprise Linux 6 Reporter: Chao Yang <chayang>
Component: qemu-kvmAssignee: Eduardo Habkost <ehabkost>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.5CC: acathrow, areis, bsarathy, chayang, ehabkost, juzhang, michen, minovotn, mkenneth, pm-rhel, qzhang, tlavigne, virt-maint
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qemu-kvm-0.12.1.2-2.415.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-21 06:04:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Chao Yang 2013-10-24 06:33:34 UTC
Description of problem:
I have a system with RHEL 6.4GA OS. Upgraded it with latest Z stream qemu-kvm and kernel packages,  then tried to migrate between it and a RHEL 6.5 system. It failed on:
"(qemu) qemu: warning: error while loading state for instance 0x0 of device 'cpu' load of migration failed" while migrating from RHEL 6.5 to RHEL 6.4.z.

Version-Release number of selected component (if applicable):
RHEL 6.4.z host(host A):
2.6.32-358.25.1.el6.x86_64
qemu-kvm-0.12.1.2-2.355.el6_4.9.x86_64

RHEL6.5 host(host B):
2.6.32-424.el6.x86_64
qemu-kvm-0.12.1.2-2.414.el6.x86_64

How reproducible:
100%

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

Actual results:
(qemu) qemu: warning: error while loading state for instance 0x0 of device 'cpu'
load of migration failed


Expected results:


Additional info:
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.4.z.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 cirrus -vnc :1

-- CPU model of host A:
processor	: 7
vendor_id	: GenuineIntel
cpu family	: 6
model		: 58
model name	: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
stepping	: 9
cpu MHz		: 1600.000
cache size	: 8192 KB
physical id	: 0
siblings	: 8
core id		: 3
cpu cores	: 4
apicid		: 7
initial apicid	: 7
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms
bogomips	: 6784.71
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:



-- CPU model of host B:
processor	: 3
vendor_id	: GenuineIntel
cpu family	: 6
model		: 42
model name	: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz
stepping	: 7
cpu MHz		: 1600.000
cache size	: 6144 KB
physical id	: 0
siblings	: 4
core id		: 3
cpu cores	: 4
apicid		: 6
initial apicid	: 6
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid
bogomips	: 6186.79
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:

Comment 2 Chao Yang 2013-10-24 07:14:19 UTC
Hi Eduardo,
 Is there additional/further info you need to debug this issue? Please feel free to needinfo me.

Comment 3 Chao Yang 2013-10-24 07:17:33 UTC
Additional info:
I tried host C with RHEL 6.4.z, then migrated from host A to host C, it succeeded. 

CPU model of host C:
processor	: 7
vendor_id	: GenuineIntel
cpu family	: 6
model		: 42
model name	: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
stepping	: 7
cpu MHz		: 1600.000
cache size	: 8192 KB
physical id	: 0
siblings	: 8
core id		: 3
cpu cores	: 4
apicid		: 7
initial apicid	: 7
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid
bogomips	: 6784.19
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:

Comment 4 Chao Yang 2013-10-24 07:26:37 UTC
Reproducible with both -cpu Nehalem and default one  when migrating from host A to host B.

Comment 6 Eduardo Habkost 2013-10-24 08:49:47 UTC
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.

Comment 7 Eduardo Habkost 2013-10-24 08:57:38 UTC
Please also check if bug is reproducible if running qemu-kvm-0.12.1.2-2.413.el6 (or older) on the RHEL-6.5 host.

Comment 8 Qunfang Zhang 2013-10-24 09:10:34 UTC
Adding "Regression" keyword first as we re-test and find qemu-kvm-386 has no problem. And also, windows guest works fine.

Comment 12 Chao Yang 2013-10-24 09:35:40 UTC
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

Comment 19 Qunfang Zhang 2013-10-25 00:22:35 UTC
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

Comment 20 Michal Novotny 2013-10-25 14:29:39 UTC
Fixed in version qemu-kvm-0.12.1.2-2.415.el6.

Michal

Comment 22 Chao Yang 2013-10-28 05:44:34 UTC
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.

Comment 24 errata-xmlrpc 2013-11-21 06:04:41 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