>
> It's not really an i/o page. All 1s means INVALID_MFN, which means the
p2m
> lookup failed. I suppose Windows may think it is a valid pfn (e.g., an
> emulated device?) but that kind of mem can't be granted and never
could be.
>
That pfn is right in the middle of normal memory - 0x2c0f, 0x2749,
0x274a are the examples I have, and the DomU has 768MB allocated to it.
I'll try and add some debug code to get the pfn back out of the grant
table when the error occurs, just in case a bug has caused the entry to
get corrupt.
So there is definitely nothing I could tell Xen to do with a DomU PFN
that would remove the p2m mapping?
Thanks
James
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel