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] auto balloon amount

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] auto balloon amount
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Wed, 14 Mar 2007 13:31:06 +0000
Delivery-date: Wed, 14 Mar 2007 06:31:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
During recent debugging I realized that the auto ballooning for PV domains
possibly provides only exactly the amount the domain is configured to
consume. This potentially leaves Xen with (almost) no domain memory,
despite the fact that this pool is (a) used for some internal allocations (at
least on x86-64) and (b) in order for dom0 (or other I/O domains) to
return contiguous memory chunks.

Wouldn't it therefore be more reasonable to at least allow some marginal
amount of memory to be left to Xen's domain pool?

Thanks, Jan

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] auto balloon amount, Jan Beulich <=