From: Alexandre DERUMIER <aderumier@odiso.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] ballooning not working on hotplugged pc-dimm
Date: Tue, 09 Sep 2014 05:05:33 +0200 (CEST) [thread overview]
Message-ID: <e8665241-6327-45ee-8762-f423cdcb7169@mailpro> (raw)
In-Reply-To: <0a98da72-f316-4e2b-8327-201f85a6e879@mailpro>
Hello,
I was playing with pc-dimm hotplug, and I notice that balloning is not working on
memory space of pc-dimm devices.
example:
qemu -m size=1024,slots=255,maxmem=15000M
#free -m : 1024M
-> qmp balloon 512M
#free -m : 512M
-> hotplug pc-dimm 1G:
#free -m : 1512M
(This is the same behavior if qemu is started with pc-dimm devices)
qemu 2.1
Guest kernel : 3.12.
Does it need a guest balloon module update ?
Regards,
Alexandre Derumier
next parent reply other threads:[~2014-09-09 3:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0a98da72-f316-4e2b-8327-201f85a6e879@mailpro>
2014-09-09 3:05 ` Alexandre DERUMIER [this message]
2014-09-10 9:00 ` [Qemu-devel] ballooning not working on hotplugged pc-dimm zhanghailiang
2014-09-11 1:57 ` Michael R. Hines
2014-09-11 6:22 ` Paolo Bonzini
2014-09-11 6:27 ` Michael R. Hines
2014-09-11 6:33 ` zhanghailiang
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=e8665241-6327-45ee-8762-f423cdcb7169@mailpro \
--to=aderumier@odiso.com \
--cc=qemu-devel@nongnu.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).