[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: Thu, 31 May 2012 17:04:27 +0200
  • Delivery-date: Thu, 31 May 2012 15:04:59 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

# HG changeset patch
# User Olaf Hering <olaf@xxxxxxxxx>
# Date 1338476618 -7200
# Node ID 4dad9647a0963a2665ccf055492e740c2b399517
# Parent  d7318231cfe3498947bf75f09d6675407d7b4e76
xl.cfg: document the maxmem= option

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

diff -r d7318231cfe3 -r 4dad9647a096 docs/man/xl.cfg.pod.5
--- a/docs/man/xl.cfg.pod.5
+++ b/docs/man/xl.cfg.pod.5
@@ -174,6 +174,14 @@ Honoured by the sedf scheduler.
 Start the guest with MBYTES megabytes of RAM.
+=item B<maxmem=MBYTES>
+Specifies the maximum amount of memory a guest can ever see.
+The value of maxmem= must be equal or greater than memory=.
+In combination with the memory= option it will start the guest "pre-ballooned".
+In a HVM guest it will enable the PoD (populate on demand) mode, iff the 
values of memory= and maxmem= differ.
+The guest needs a balloon driver in this case, without a balloon driver it 
will crash.
 =item B<on_poweroff="ACTION">
 Specifies what should be done with the domain if it shuts itself down.
@@ -971,10 +979,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®.