* [PATCH] docs: Mention a common pitfall in ballooning
@ 2015-03-19 17:09 George Dunlap
2015-03-20 11:57 ` Ian Campbell
0 siblings, 1 reply; 2+ messages in thread
From: George Dunlap @ 2015-03-19 17:09 UTC (permalink / raw)
To: xen-devel; +Cc: George Dunlap, Ian Jackson, Wei Liu, Ian Campbell
Several users have reported that their available free memory in the
guest when they used maxmem >> memory was much smaller than when
maxmem == memory. This is the unavoidable consequence of how
ballooning works, but it's not something users expect.
Warn them of this effect in the place we tell them how to make it
happen, so they aren't surprised.
Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
---
CC: Ian Campbell <ian.campbell@citrix.com>
CC: Ian Jackson <ian.jackson@citrix.com>
CC: Wei Liu <wei.liu2@citrix.com>
---
docs/man/xl.cfg.pod.5 | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/docs/man/xl.cfg.pod.5 b/docs/man/xl.cfg.pod.5
index 93cd7d2..4432f95 100644
--- a/docs/man/xl.cfg.pod.5
+++ b/docs/man/xl.cfg.pod.5
@@ -264,6 +264,13 @@ if the values of B<memory=> and B<maxmem=> differ.
A "pre-ballooned" HVM guest needs a balloon driver, without a balloon driver
it will crash.
+NOTE: Because of the way ballooning works, the guest has to allocate
+memory to keep track of maxmem pages, regardless of how much memory it
+actually has available to it. A guest with maxmem=262144 and
+memory=8096 will report significantly less memory available for use
+than a system with maxmem=8096 memory=8096 due to the memory overhead
+of having to track the unused pages.
+
=back
=head3 Guest Virtual NUMA Configuration
--
1.9.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] docs: Mention a common pitfall in ballooning
2015-03-19 17:09 [PATCH] docs: Mention a common pitfall in ballooning George Dunlap
@ 2015-03-20 11:57 ` Ian Campbell
0 siblings, 0 replies; 2+ messages in thread
From: Ian Campbell @ 2015-03-20 11:57 UTC (permalink / raw)
To: George Dunlap; +Cc: Ian Jackson, Wei Liu, xen-devel
On Thu, 2015-03-19 at 17:09 +0000, George Dunlap wrote:
> Several users have reported that their available free memory in the
> guest when they used maxmem >> memory was much smaller than when
> maxmem == memory. This is the unavoidable consequence of how
> ballooning works, but it's not something users expect.
>
> Warn them of this effect in the place we tell them how to make it
> happen, so they aren't surprised.
>
> Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
acked + applied, thanks.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-03-20 11:57 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-03-19 17:09 [PATCH] docs: Mention a common pitfall in ballooning George Dunlap
2015-03-20 11:57 ` Ian Campbell
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.