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

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

If this is a PAE system then L3 entries only have the present/valid bit --
there's certainly no r/w bit. Try upgrading to tip of xen-3.1-testing (c/s
15564) as that has definitely passed regression tests (which involves
creating quite a number of domains). Perhaps we have a bad interaction with
VMware.

 -- Keir

On 25/12/07 01:40, "Kip Macy" <kip.macy@xxxxxxxxx> wrote:

> 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



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