From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 190211] New: memory ballooning doesn't take on boot since approx kernel 4.5.3
Date: Tue, 13 Dec 2016 00:43:20 +0000 [thread overview]
Message-ID: <bug-190211-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=190211
Bug ID: 190211
Summary: memory ballooning doesn't take on boot since approx
kernel 4.5.3
Product: Virtualization
Version: unspecified
Kernel Version: 4.9, 4.8.14, 4.8.1, 4.7.2, 4.6.2
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: ap@zip.com.au
Regression: No
Just noticed that on restart or bootup memory ballooning stopped working. The
guest boots with the maximum allowed memory rather than the "current" setting
in libvirt.
If I request a memory shrink after boot, the balloon works and memory available
shrinks as requested.
I went through the following guest kernels: 4.9, 4.8.14, 4.8.1, 4.7.2, 4.6.2,
4.5.3 (worked), 4.4.4 (worked). These were custom compiles. Debian official
kernels for 4.8.0 and 4.7.0 also failed.
I used libvirt 2.5.0, 2.4.0 and 1.2.20
Qemu versions: 2.5 and 2.7
Debian stretch for the guest, wheezy and stretch for the host.
Host kernels 4.3.3, 4.8.6 and 4.8.14
The fact that dropping kernel versions made it work once I hit 4.5.3 makes me
think there's an issue kernel-side.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2016-12-13 0:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 0:43 bugzilla-daemon [this message]
2016-12-13 0:44 ` [Bug 190211] memory ballooning doesn't take on boot since approx kernel 4.5.3 bugzilla-daemon
2016-12-14 23:28 ` bugzilla-daemon
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@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 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.