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

[Xen-devel] [PATCH] xl.cfg: document the maxmem= option

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Olaf Hering <olaf@xxxxxxxxx>
  • Date: Fri, 04 May 2012 21:31:42 +0200
  • Delivery-date: Fri, 04 May 2012 19:32:18 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

# HG changeset patch
# User Olaf Hering <olaf@xxxxxxxxx>
# Date 1336159720 -7200
# Node ID c414728d0d12f1c3e416e40cceefca2f0b00578e
# Parent  8f556a70ae0bef47e242f9e7be0a054769fc8277
xl.cfg: document the maxmem= option

Signed-off-by: Olaf Hering <olaf@xxxxxxxxx>

diff -r 8f556a70ae0b -r c414728d0d12 docs/man/xl.cfg.pod.5
--- a/docs/man/xl.cfg.pod.5
+++ b/docs/man/xl.cfg.pod.5
@@ -484,6 +484,14 @@ are not using hardware assisted paging (
 mode) and your guest workload consists of a a very large number of
 similar processes then increasing this value may improve performance.
+=item B<maxmem=MBYTES>
+Specifies the maximum amount of memory the HVM guest can ever see.
+In combination with the memory= option it will enable the PoD (populate
+on demand) mode for the guest iff the values of memory= and maxmem=
+differ. The guest needs a balloon driver in this case. The value of
+maxmem= must be equal or greater than memory=.
 =head3 Processor and Platform Features
@@ -955,10 +963,6 @@ XXX
-=item B<maxmem=NUMBER>
 =item B<nodes=XXX>

Xen-devel mailing list



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