Hi Pier The only thing I can tell that is, seems guest completely messed up... It ran into some non-code segment.
> unhandled vm exit: 0x80000021 vcpu_id 0 > rax 0000000000000007 rbx 0000000000001490 rcx 0000000000000000 rdx > 00000000000019a0 rsi 0000000000000000 rdi 0000000000000000 rsp > 0000000000000080 rbp 00000000000096bf r8 0000000000000000 r9 > 0000000000000000 r10 0000000000000000 r11 0000000000000000 r12 > 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 > 0000000000000000 rip 000000000000002a rflags 00023202 > cs 14a2 (00000000/00000000 p 0 dpl 0 db 0 s 0 type 9 l 0 g 0 avl 0) > ds 19a0 (00000000/00000000 p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) > es 1a31 (00000000/00000000 p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) > ss 1a29 (00000000/00000000 p 0 dpl 0 db 0 s 0 type 1 l 0 g 0 avl 0) Segments maybe messed up... > fs 0000 (00000000/00000000 p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) > gs 0000 (00000000/00000000 p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) > tr 0058 (00201ffa/0000ffff p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) > ldt 0000 (00000000/00000000 p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) > gdt 200000/1dd8 > idt 201df0/188 > cr0 80000019 cr2 0 cr3 1440000 cr4 0 cr8 0 efer 0 CR0.PE set(sorry for wrong decode before...), CR0.PG set. Guest in protected mode. But CR4 is wrong, at least CR4.PAE and CR4.VMXE should be set. > code: 00 f0 53 ff 00 f0 53 ff 00 f0 a5 fe 00 f0 87 e9 00 f0 53 ff --> 00 f0 > 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 57 ef 00 f0 53 ff 00 f0 3a 83 00 c0 4d > f8 00 f0 Seems like meaningless code... Well, still don't know what the "checkpoint" done caused this... At least it seems more than a emulation bug. Anybody else have idea?... -- regards Yang, Sheng -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
