[Xen-devel] Xen bug or VMware bug?

To:	xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] Xen bug or VMware bug?
From:	"Kip Macy" <kip.macy@xxxxxxxxx>
Date:	Mon, 24 Dec 2007 16:39:27 -0800
Delivery-date:	Mon, 24 Dec 2007 16:39:50 -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:mime-version:content-type:content-transfer-encoding:content-disposition; bh=dgUaCGav/uq9m1M1BgOP6/jblQhXUP3yRRn/HvDh/lA=; b=JUDxRcvvqGCo72aGysCmzdregMdOTyuFCXWtIDuxzmoTNBNdn/HhEYtCgIsMrOnCJAONzm0+lhc5N/R1DV+EOO3kNYHAiyob+YBBslVvmCPYN4/imZPZYWLYp8WN+lcGDX2hW89Y8QmVbjaeNf4YiWBMvpDnFe3T45vjLlpwQsU=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=BOVWU+uls8wygc0OIH7kCQ/MV8LRZgwIvRxIUJlIevKDdxriz0XLZC6YWYAfHnBslCOJ1j0C4QGzlbVG4zXi4tI/4uF/3uOmEf4/4Y+RaGy6a0CnbmBmdxVNSssHWpZ9AIidniPKGaP0EOZIM46BYdui4uibrP5JR3dpP3HWWAM=
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

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