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


Re: [Xen-devel] Error restoring DomU when using GPLPV

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Error restoring DomU when using GPLPV
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 04 Aug 2009 09:21:05 +0100
Cc: Joshua West <jwest@xxxxxxxxxxxx>
Delivery-date: Tue, 04 Aug 2009 01:22:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D016DE055@trantor>
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: AcoUog43ZhCRzTxFSPuGfTBNvaTQKgAAoXawAAfYLBAAAY5aQAADuI5wAADcjpY=
Thread-topic: [Xen-devel] Error restoring DomU when using GPLPV
User-agent: Microsoft-Entourage/
On 04/08/2009 08:58, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

> When the DomU is running, 'xm debug q' looks like:
> (XEN) General information for domain 23:
> (XEN)     refcnt=3 dying=0 nr_pages=197611 xenheap_pages=33
> dirty_cpus={1} max_pages=197632
> During restore, it looks like this:
> (XEN) General information for domain 22:
> (XEN)     refcnt=3 dying=0 nr_pages=196576 xenheap_pages=5 dirty_cpus={}
> max_pages=197632

Is the host simply out of memory? If dom22 above has 196576 pages and
max_pages=197632 then an allocation of 33 order-0 extents should not fail
due to over-commitment to the guest. The only reason for such a failure is
inadequate memory available in the host free pools. Perhaps xend
auto-ballooning is involved? I'd turn it off if so, as it blows. It could
have freed up one-page-too-few or somesuch.

 -- Keir

Xen-devel mailing list