WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] VMX status report 12542:91951de7592c

To: "Keir Fraser" <keir@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] VMX status report 12542:91951de7592c
From: "Yu, Ping Y" <ping.y.yu@xxxxxxxxx>
Date: Wed, 29 Nov 2006 14:24:04 +0800
Delivery-date: Tue, 28 Nov 2006 22:24:54 -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: AccRzW1PE3gfF9VARKiKLg//5KS2wgAJ7ldgAAFnUOIANWLE8AABFSXgAAsd03UAH2B/YA==
Thread-topic: [Xen-devel] VMX status report 12542:91951de7592c
>
>I added some more tracing in c/s 12591. However, you can expect for the
>"Access faulted on page boundary" message to appear occasionally.
Crucially
>we expect to see the printed 'ea' value be a little bit smaller than
the
>printed 'cr2' value (by up to 7 bytes).
Here is the latest output for the issue and at the mean time, we found
UP Linux VMX
could not boot successfully
(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
....
(XEN) sh error: sh_remove_shadows(): can't find all shadows of mfn a396e
(shadow_flags=00001000)
(XEN) domain_crash called from common.c:2103
(XEN) Domain 166 (vcpu#0) crashed on cpu#0:

>
>If the extra tracing doesn't turn up anything interesting I'll quieten
it
>down again later this week.
>
> -- Keir

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