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

To:	xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] Re: Xen bug or VMware bug?
From:	"Kip Macy" <kip.macy@xxxxxxxxx>
Date:	Mon, 24 Dec 2007 17:40:44 -0800
Delivery-date:	Mon, 24 Dec 2007 17:41:07 -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=mI40hJIhp0qqJFbChCys7rfLwxXA2O/IJY5NKu+HlQQ=; b=d8xA4PjLQCbmuT7KsydV+Y8ZQPb7haGuEjYuD7TJxfubkxQ17OtCBPlXbSiPBE2okYyaMaN8ez8+FDgWgU4MRVeuVFVcoEg8UFY+xQJVPAeKB8PURvo2Tm/Inj432QO8yA772VT7rvqWU1HxXhheDHXdVIxPQKVf93Sais4Cvhk=
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=orE2EUS8B8Kzwb5fn7HFSGjHhQYRiGUfDJcX7yp9M6KILScufmOlbWJH8ZGGgvO3FFbbw2mzl7pJH8tjxmwj28xp0A9JDXAJtWMgqCiSGhrPjXd2J/Yz3ZQw2GTiG+wttwv/bB26vvI8daKVZ3TMhlLNqA0lfx3ZSTzHRPk55og=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<b1fa29170712241639x21aa07d8y17fe4699945e6703@xxxxxxxxxxxxxx>
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>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Actually, it turns out that it occurs slightly further up. Trying to
add a page directory with only the valid flag set seems to make Xen
unhappy (i.e. system reset). Setting the R/W flag doesn't seem to work
as it complains:

(XEN) mm.c:1477:d1 Bad L3 flags 2

In any event I'll figure out what the right incantation is, but it
appears you may have a legitimate hole at the moment.

 -Kip


On Dec 24, 2007 4:39 PM, Kip Macy <kip.macy@xxxxxxxxx> wrote:
> I'm running a fairly recent version of xen:
>
> [kmacy@xen0 xen-3.1-testing.hg]$ hg tip
> changeset:   15547:f4dc0d3dfb0f
> tag:         tip
> user:        Keir Fraser <keir.fraser@xxxxxxxxxx>
> date:        Sat Dec 08 17:23:05 2007 +0000
> summary:     Update version tag to 3.1.3-rc1-devel (nearly ready for -rc1).
>
> I'm currently doing bring-up inside of a VMware VM. The VM resets
> itself with a stack fault when I execute a MMUEXT_PIN_L1_TABLE.
>
> 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
>
> All it takes for me is 'xm create xmexample1' to cause dom0 to be reset.
>
>
> Thanks.
>
>  -Kip
>

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