From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xensource.com
Subject: [PATCH] xl.cfg: document the maxmem= option
Date: Thu, 31 May 2012 17:04:27 +0200 [thread overview]
Message-ID: <4dad9647a0963a2665cc.1338476667@probook.site> (raw)
# HG changeset patch
# User Olaf Hering <olaf@aepfle.de>
# Date 1338476618 -7200
# Node ID 4dad9647a0963a2665ccf055492e740c2b399517
# Parent d7318231cfe3498947bf75f09d6675407d7b4e76
xl.cfg: document the maxmem= option
Signed-off-by: Olaf Hering <olaf@aepfle.de>
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
XXX
-=item B<maxmem=NUMBER>
-
-XXX
-
=item B<nodes=XXX>
XXX
next reply other threads:[~2012-05-31 15:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 15:04 Olaf Hering [this message]
2012-06-01 11:05 ` [PATCH] xl.cfg: document the maxmem= option Ian Campbell
2012-06-01 14:59 ` Olaf Hering
-- strict thread matches above, loose matches on Subject: below --
2012-06-01 14:55 Olaf Hering
2012-06-06 12:54 ` Ian Campbell
2012-05-04 19:31 Olaf Hering
2012-05-04 19:42 ` Konrad Rzeszutek Wilk
2012-05-04 20:18 ` Olaf Hering
2012-05-06 9:35 ` Ian Campbell
2012-05-07 13:06 ` Olaf Hering
2012-05-07 16:37 ` Dan Magenheimer
2012-05-08 12:41 ` Ian Campbell
2012-05-08 15:40 ` Dan Magenheimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4dad9647a0963a2665cc.1338476667@probook.site \
--to=olaf@aepfle.de \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).