Hi,
Does anyone have any idea on a issue that I have regarding VM migration from AMD to Intel host?
When the guest is migrated from AMD host and right after it starts on Intel host,
qemu process crashes with log messages like below.
Looks like, when the guest is loaded on its network, it is more likely to manifests the issue.
Platform is CentOS 5.4(x86_64) without any updates both for the hosts and the guest,
and KVM related packages are the following:
kernel–2.6.18–164.el5
kmod-kvm–83–105.el5_4.9
kvm–83–105.el5_4.9
I'd appreciate any info on this issue.
-------------------------
LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin HOME=/root USER=root LOGNAME=root /usr/libexec/qemu-kvm -S -M pc -m 1024
-smp 1 -name stress-test-4 -uuid 425edb11-be36-46c5-b8b6-2570f09a3f27 -no-kvm-pit-reinjection -monitor pty -pidfile
/var/ru
n/libvirt/qemu//stress-test-4.pid -boot cd -drive file=/data/images/stress-test-4.img,if=ide,index=0,boot=on -drive file=/data/iso/CentOS-5.4-x86_64-bin-DVD.iso,if=ide,media=cdrom,index=2 -drive file=/data/images/stdisk-4-1.img,if=virtio,index=0 -drive file=/data/images/stdisk-4-2.img,if=virtio,index=1 -net nic,macaddr=00:42:5e:27:3f:9a,vlan=0,model=virtio -net tap,fd=18,script=,vlan=0,ifname=vnet2 -serial none -parallel none -usb -vnc 0.0.0.0:2 -k ja -incoming tcp:0.0.0.0:49213 213 0.0.0:49213 0.0.0:49213 213 0:49213 ja -incoming tcp:0.0.0.0:49213 213
char device redirected to /dev/pts/1
unhandled vm exit: 0x80000021 vcpu_id 0
rax 0000000000000001 rbx ffff81003dcd7d00 rcx ffff81003e0cc000 rdx 000000000000c050
rsi 000000000001c050 rdi 0000000000000001 rsp ffff81001db31960 rbp ffff81001bbca080
r8 0000000000000000 r9 ffff81003e0cc000 r10 0000000000000220 r11 ffffffff881cf53d
r12 ffff81003dcd7800 r13 ffff81003b853c00 r14 ffff81003dcd7a00 r15 00000001083e14c5
rip ffffffff80151895 rflags 00000246
cs 0010 (00000000/ffffffff p 1 dpl 0 db 0 s 1 type b l 1 g 1 avl 0)
ds 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
es 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
ss 0018 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0)
fs 0063 (42a37940/ffffffff p 1 dpl 3 db 1 s 1 type 2 l 0 g 1 avl 1)
gs 0000 (ffffffff803c0000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
tr 0040 (ffff810001573000/0000206f p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
ldt 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
gdt ffffffff803f2000/80
idt ffffffff80442000/fff
cr0 8005003b cr2 3a9ce9a070 cr3 1dba6000 cr4 6e0 cr8 0 efer d01
-------------------------
--- cpuinfoon AMD
processor : 0
vendor_id : AuthenticAMD
cpu family : 16
model : 2
model name : Quad-Core AMD Opteron(tm) Processor 1354
stepping : 3
cpu MHz : 1100.000
cache size : 512 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc nonstop_tsc pni cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy altmovcr8 abm sse4a misalignsse 3dnowprefetch osvw
bogomips : 4399.99
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate [8]
---- cpuinfo on Intel
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Xeon(R) CPU X3210 @ 2.13GHz
stepping : 11
cpu MHz : 1600.000
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
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 syscall nx lm constant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm
bogomips : 4256.12
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
TIA,
Tomoe
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
