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
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel