This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] touching a missing page causes DomU to die

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] touching a missing page causes DomU to die
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Fri, 21 Jan 2011 23:34:34 +1100
Delivery-date: Fri, 21 Jan 2011 04:35:31 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acu5Z48OMwafBpkVQ8GiBESrTYPULg==
Thread-topic: touching a missing page causes DomU to die
My Windows PV drivers are crashing during hibernation, and I've finally
figured out that it's because the windows hibernation mode driver double
buffers memory before handing it to my block device driver, and in doing
so 'touches' some pages of memory I have given back to xen (to work
around a domu save crash).

I assume that this is the same issue that causes touching unpopulated
PoD memory to blow up the DomU too.

I don't know if there is a way to mark the pages I gave back to xen as
'gone' under windows, the best I can do is allocate them to my driver...
any suggestions as to how to resolve it from xen? One idea I had was to
map the same physical page of memory into the 'holes' so things at least
don't blow up, but I'm not sure if that is possible or desirable.



Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>