[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] "Iomem mapping not permitted" during windows crash dump under GPLPV


  • To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Sat, 30 Jan 2010 19:30:28 +1100
  • Cc:
  • Delivery-date: Sat, 30 Jan 2010 00:31:15 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcqhbLbcrWW9KgunS7SmLR6WJEIH7AAGLs0KAAAGXMA=
  • Thread-topic: [Xen-devel] "Iomem mapping not permitted" during windows crash dump under GPLPV

> 
> 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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.