[Bug 63121] New: The guest will hang after live migration.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.kernel.org/show_bug.cgi?id=63121

            Bug ID: 63121
           Summary: The guest will hang after live migration.
           Product: Virtualization
           Version: unspecified
    Kernel Version: 3.12.0-rc2
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@xxxxxxxxxxxxxxxxxxxx
          Reporter: chao.zhou@xxxxxxxxx
        Regression: No

Environment:
------------
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux
kvm.git Commit:7854cbca815562a49d50bbc6f31599312853d1f4
qemu.git Commit:1cdae4573d7613149348d834c605bfbe3c7d405b
Host Kernel Version:3.12.0-rc2


Bug detailed description:
--------------------------
after guest live migration, the guest will hang, and in command line some
message about "KVM: entry failed, hardware error 0x80000021" will print

note:
1. after guest save/restore, the guest will hang
2. This should be a kernel bug
kvm      + qemu     =  result
7854cbca + 1cdae457 =  bad
2f303b74 + 1cdae457 =  good

Reproduce steps:
----------------
1.Start a TCP daemon for migration
qemu-system-x86_64 -enable-kvm -m 2048 -smp 2 -net none /root/rhel6u4.qcow
2. create guest
qemu-system-x86_64 -enable-kvm -m 2048 -smp 2 -net none /root/rhel6u4.qcow
-incoming tcp:localhost:4444
3. ctrl+alt+2 to change to qemu monitor
4. migrate tcp:localhost:4444


Current result:
----------------
guest hang, and print "KVM: entry failed, hardware error 0x80000021"

Expected result:
----------------
after live/migration or save/restore, the guest works fine

Basic root-causing log:
----------------------
after live/migration or save/restore, the command line will print:

KVM: entry failed, hardware error 0x80000021

If you're running a guest on an Intel machine without unrestricted mode
support, the failure can be most likely due to the guest entering an invalid
state for Intel VT. For example, the guest maybe running in big real mode
which is not supported on less recent Intel processors.

EAX=00000000 EBX=00000000 ECX=00000000 EDX=00000000
ESI=00000001 EDI=81de1228 EBP=81a01ec8 ESP=81a01ec8
EIP=8103b90b EFL=00000246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0000 00000000 0000ffff 00009300
CS =f000 ffff0000 0000ffff 00009b00
SS =0000 00000000 0000ffff 00009300
DS =0000 00000000 0000ffff 00009300
FS =0000 00000000 0000ffff 00009300
GS =0000 00000000 0000ffff 00009300
LDT=0000 00000000 0000ffff 00008200
TR =0000 00000000 0000ffff 00008b00
GDT=     00000000 0000ffff
IDT=     00000000 0000ffff
CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000000
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000
DR3=0000000000000000
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000000
Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
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




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux