This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] VMX status report 10680:f692a0a476c5

To: "Stefan Kaltenbrunner" <stefan@xxxxxxxxxxxxxxxx>, "Zheng, Jeff" <jeff.zheng@xxxxxxxxx>
Subject: RE: [Xen-devel] VMX status report 10680:f692a0a476c5
From: "Li, Xin B" <xin.b.li@xxxxxxxxx>
Date: Sat, 15 Jul 2006 09:00:14 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 14 Jul 2006 18:01:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcanXvmQCqRJJJlQSuS79CoNJQSLoQASvjXQ
Thread-topic: [Xen-devel] VMX status report 10680:f692a0a476c5
>FYI: on my Pentium D920 box with a 64bit hypervisor WinXP SP2 is broken
>on -unstable for a while now:
>(XEN) ff, This opcode isn't handled yet!
>(XEN) handle_mmio: failed to decode instruction
>(XEN) mmio opcode: va 0xb8216, gpa 0xb8216, len 3: ff 77 16
>(XEN) domain_crash_sync called from platform.c:857
>(XEN) Domain 6 (vcpu#0) crashed on cpu#0:
>(XEN) ----[ Xen-3.0-unstable    Not tainted ]----
>(XEN) CPU:    0
>(XEN) RIP:    c000:[<0000000000003c09>]
>(XEN) RFLAGS: 0000000000033006   CONTEXT: hvm
>(XEN) rax: 00000000000f0060   rbx: 0000000000000200   rcx: 
>(XEN) rdx: 0000000000000000   rsi: 0000000000000000   rdi: 
>(XEN) rbp: 00000000000dffcc   rsp: 000000000000ffb8   r8:  
>(XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 
>(XEN) r12: 0000000000000000   r13: 0000000000000000   r14: 
>(XEN) r15: 0000000000000000   cr0: 0000000000050032   cr3: 
>(XEN) ds: b800   es: 0000   fs: 0010   gs: 0010   ss: 0000   cs: c000
>the very same issue affects my Fedora Core 5 VMX domain.

Fixed by changeset 10704.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>