[Xen-devel] Re: Xen bug or VMware bug?

To:	"Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] Re: Xen bug or VMware bug?
From:	"Kip Macy" <kip.macy@xxxxxxxxx>
Date:	Tue, 25 Dec 2007 02:16:43 -0800
Delivery-date:	Tue, 25 Dec 2007 02:17:04 -0800
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=DYk9PIVrF+icFUIU5XFLX4GyAHABwDouRpRLE49MMfc=; b=M43pYwFqeE4/DF3c3WSrzFdGqMcTNnxrJlz56FVZjiBoEMujGh7MY0VK1dfoyxGB5LSoWG/kLX6DEpP48G38sYT0kJ/h2OHH26X+C1m46nK7yT5IVGnE/H9ffbP0GJDPuSUoRKKDdckcDDsdkG5wrnlJ2jn6n0qpKDGbUjIXHyk=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JmUP7OpoS0dZSTQIk/+QRjpj8aCKNGF03Rze5Pb5VvrlX9vxr2aqCloiSWVMU4SUiajeaNmEZ29EtIYLDwRQ6G2E1Je8cAuL2XWZxTQykqu+FbGyay24UZNu/sa3SiPMW7S/8ETnUIJJWGh4cG4LRVyttaILfP5y2YnNBv1KNmQ=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<C39681C4.1A2CF%Keir.Fraser@xxxxxxxxxxxx>
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:	<b1fa29170712241639x21aa07d8y17fe4699945e6703@xxxxxxxxxxxxxx> <C39681C4.1A2CF%Keir.Fraser@xxxxxxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Correct. Just start it up on a PAE xen.

As it turns out *any* in-place updates to the L3 - even putting a zero
where there is currently a zero - will cause a system reset. At least
on VMWare Fusion. I've worked around it for the moment by allocatng a
new L3 and then switching to that.

   -Kip

On 12/25/07, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
> On 25/12/07 00:39, "Kip Macy" <kip.macy@xxxxxxxxx> wrote:
>
> > Has any bug that could be causing this been fixed recently? If not
> > could someone do me a quick favor and try out:
> >
> > http://www.fsmware.com/xenofreebsd/stackfault/xen.tgz
>
> I've downloaded it. I assume I try to create this with PAE Xen and PAE dom0?
> I'll try a bit later this week.
>
>  -- Keir
>
>
>

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

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] Re: Xen bug or VMware bug?