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] Crash in hypercall_xlat_continuation with 64bit xen 3.1.

To: "Kurt C. Hackel" <kurt.hackel@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Jan Beulich" <jbeulich@xxxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] Crash in hypercall_xlat_continuation with 64bit xen 3.1.1 when migrating a 32bit pv guest
From: "Ian Pratt" <Ian.Pratt@xxxxxxxxxxxxx>
Date: Fri, 7 Dec 2007 21:47:15 -0000
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>
Delivery-date: Fri, 07 Dec 2007 13:47:58 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4759B5A8.7070801@xxxxxxxxxx>
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>
References: <4759B5A8.7070801@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acg5FawohVKNjFvUQYSa4GXlRRrFnwABLZJA
Thread-topic: [Xen-devel] Crash in hypercall_xlat_continuation with 64bit xen 3.1.1 when migrating a 32bit pv guest
> I'm seeing a crash in 64bit xen when doing live migration of a 32bit
pv
> guest under load.  The crash does not occur without the load, it
> happens with both Red Hat/Oracle and Xensource kernels (el4u5 in this
case),
> and it takes about 3-5 migrations to trigger the bug.
> Below you'll see that the 32bit guest ebx register, stored here in the
> 64bit reg variable, is supposed to have the upper 32bits cleared, but
> it has 0x00000080 in the upper 32bits.

Have you tried pulling through this patch?

http://xenbits.xensource.com/xen-unstable.hg?rev/46776e65e679

Ian


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

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