RE: [Xen-devel] VMX status report 12591:7826e5482d42 with BLOCK

To:	"Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	RE: [Xen-devel] VMX status report 12591:7826e5482d42 with BLOCK issue
From:	"Yu, Ping Y" <ping.y.yu@xxxxxxxxx>
Date:	Wed, 29 Nov 2006 16:21:15 +0800
Delivery-date:	Wed, 29 Nov 2006 00:21:48 -0800
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:	AccTXyTTdu2H8bVhStSWLYmtNEaxIQAHEbmwAARjECgAAJQJ4A==
Thread-topic:	[Xen-devel] VMX status report 12591:7826e5482d42 with BLOCK issue

Here it is.

Ping
>
>On 29/11/06 6:16 am, "Yu, Ping Y" <ping.y.yu@xxxxxxxxx> wrote:
>
>> 1).In x86 64 bits mode: Base kernel Linux guest OS crash, and "xm
dmesg"
>> complains:
>> (XEN) x86_emulate.c:1224:d166 Access faulted on page boundary
>> (cr2=ffffffff80101000,ea=80101004).
>> (XEN) x86_emulate.c:461:d166 Instr: 48 c7 05 8d 0b fe ff 00 00 00 00
eb
>> 2e 48 b8 ff
>> ....
>
>Can you send more output from this crash? There will be a register dump
>immediately after the above lines.
>
> -- Keir

base_kernel.log
Description: base_kernel.log

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

xen-devel

RE: [Xen-devel] VMX status report 12591:7826e5482d42 with BLOCK issue