From: PGNet Dev <pgnet.dev@gmail.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: repeating 'd1v0 Over-allocation for domain 1' messages in xen 4.7 Host logs on PVHVM Guest launch
Date: Tue, 5 Jul 2016 07:13:42 -0700 [thread overview]
Message-ID: <85f4b2df-8951-ea20-7209-b7acd28a2da4@gmail.com> (raw)
In-Reply-To: <4328e446-8ca9-443d-c862-e24f4a797c4f@citrix.com>
Reading @
How to know if the balloon driver is running
http://www.gossamer-threads.com/lists/xen/users/315064#315064
"...
IIRC the core balloon driver is always present when Xen is enabled and
so the kernel will respond to requests from the host/toolstack to change
the amount of RAM (e.g "xm/xl mem-set foo" in dom0, which would result
in changes to /proc/meminfo).
In order to get in-guest access to control ballooning you need to
CONFIG_XEN_BALLOON enable and load the xen-balloon.ko module. I'm not
sure but I think with modern kernels this will appear in /sys and
not /proc.
...
AFAIK the balloon driver is started if you just have CONFIG_XEN.
LIke I said before CONFIG_XEN_BALLOON enables additional support for
controlling the balloon driver from within the guest (as opposed to from
the host toolstack).
..."
in the Guest,
grep -i config_xen= /boot/*config*
/boot/config-4.4.0-28-generic:CONFIG_XEN=y
grep -i xen /boot/*config* | grep -i balloon
>> /boot/config-4.4.0-28-generic:CONFIG_XEN_BALLOON=y
/boot/config-4.4.0-28-generic:CONFIG_XEN_SELFBALLOONING=y
/boot/config-4.4.0-28-generic:CONFIG_XEN_BALLOON_MEMORY_HOTPLUG=y
/boot/config-4.4.0-28-generic:CONFIG_XEN_BALLOON_MEMORY_HOTPLUG_LIMIT=512
find /sys /proc -type d | grep -i balloon | grep xen
/sys/devices/system/xen_memory/xen_memory0/selfballoon
/proc/sys/xen/balloon
ls -al /proc/sys/xen/balloon
hotplug_unpopulated
How do you blacklist the Guest ballooning?
Perhaps related? Not clear 2 me that it's the same issue,
xen/balloon: cancel ballooning if adding new memory failed
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3dcf63677d4eb7fdfc13290c8558c301d2588fe8
There's also balloon-related comments at
http://wiki.xenproject.org/wiki/XenParavirtOps
although they now look somewhat out of date w.r.t. current 4x kernel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-07-05 14:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 0:06 repeating 'd1v0 Over-allocation for domain 1' messages in xen 4.7 Host logs on PVHVM Guest launch PGNet Dev
2016-06-29 10:07 ` Jan Beulich
2016-06-29 12:58 ` PGNet Dev
2016-06-29 14:10 ` PGNet Dev
2016-06-29 14:17 ` Jan Beulich
2016-06-29 15:38 ` PGNet Dev
2016-06-29 15:59 ` Jan Beulich
2016-06-29 16:27 ` PGNet Dev
2016-07-04 11:22 ` George Dunlap
2016-07-04 14:58 ` PGNet Dev
2016-07-05 13:35 ` George Dunlap
2016-07-05 14:13 ` PGNet Dev [this message]
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=85f4b2df-8951-ea20-7209-b7acd28a2da4@gmail.com \
--to=pgnet.dev@gmail.com \
--cc=george.dunlap@citrix.com \
--cc=xen-devel@lists.xen.org \
/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).