From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 190211] memory ballooning doesn't take on boot since approx kernel 4.5.3
Date: Wed, 14 Dec 2016 23:28:59 +0000 [thread overview]
Message-ID: <bug-190211-28872-auC9NwU86F@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-190211-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=190211
--- Comment #1 from ap@zip.com.au ---
I've done a bit more poking around with kernel 4.9.
It appears that enabling NUMA on the guest kernel but /not/ using it (ie I've
not configured numa use via libvirt in qemu) is enough to fix this. The kernel
gets the lowered memory on reboot and on boot.
Is this how it is meant to function or is this still a bug?
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2016-12-14 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 0:43 [Bug 190211] New: memory ballooning doesn't take on boot since approx kernel 4.5.3 bugzilla-daemon
2016-12-13 0:44 ` [Bug 190211] " bugzilla-daemon
2016-12-14 23:28 ` bugzilla-daemon [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=bug-190211-28872-auC9NwU86F@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.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