From: Luiz Capitulino <lcapitulino@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: zhanghailiang <zhang.zhanghailiang@huawei.com>,
qemu-devel@nongnu.org, hangaohuai@huawei.com,
peter.huangpeng@huawei.com, kvm@vger.kernel.org,
imammedo@redhat.com, pkrempa@redhat.com, eblake@redhat.com,
mst@redhat.com
Subject: Re: [BUG] Balloon malfunctions with memory hotplug
Date: Mon, 2 Mar 2015 14:04:54 -0500 [thread overview]
Message-ID: <20150302140454.70a2006b@redhat.com> (raw)
In-Reply-To: <20150302062234.GG26196@grmbl.mre>
On Mon, 2 Mar 2015 11:52:34 +0530
Amit Shah <amit.shah@redhat.com> wrote:
> > >Another important detail is that, I *suspect* that a very similar
> > >bug already exists with 32-bit guests even without memory
> > >hotplug: what happens if you assign 6GB to a 32-bit without PAE
> > >support? I think the same problem we're seeing with memory
> > >hotplug will happen and solution 1 won't fix this, although
> > >no one seems to care about 32-bit guests...
>
> Not just 32-bit guests; even 64-bit guests restricted with mem= on the
> cmdline.
You're right. So, it's an already existing issue that becomes very
apparent with memory hotplug.
> I know we've discussed this in the past, and I recall
> virtio-balloon v2 was going to address this all; sadly I've not kept
> uptodate with it.
Me neither :(
WARNING: multiple messages have this Message-ID (diff)
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: hangaohuai@huawei.com, pkrempa@redhat.com,
zhanghailiang <zhang.zhanghailiang@huawei.com>,
kvm@vger.kernel.org, mst@redhat.com, peter.huangpeng@huawei.com,
qemu-devel@nongnu.org, imammedo@redhat.com
Subject: Re: [Qemu-devel] [BUG] Balloon malfunctions with memory hotplug
Date: Mon, 2 Mar 2015 14:04:54 -0500 [thread overview]
Message-ID: <20150302140454.70a2006b@redhat.com> (raw)
In-Reply-To: <20150302062234.GG26196@grmbl.mre>
On Mon, 2 Mar 2015 11:52:34 +0530
Amit Shah <amit.shah@redhat.com> wrote:
> > >Another important detail is that, I *suspect* that a very similar
> > >bug already exists with 32-bit guests even without memory
> > >hotplug: what happens if you assign 6GB to a 32-bit without PAE
> > >support? I think the same problem we're seeing with memory
> > >hotplug will happen and solution 1 won't fix this, although
> > >no one seems to care about 32-bit guests...
>
> Not just 32-bit guests; even 64-bit guests restricted with mem= on the
> cmdline.
You're right. So, it's an already existing issue that becomes very
apparent with memory hotplug.
> I know we've discussed this in the past, and I recall
> virtio-balloon v2 was going to address this all; sadly I've not kept
> uptodate with it.
Me neither :(
next prev parent reply other threads:[~2015-03-02 19:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 19:26 [BUG] Balloon malfunctions with memory hotplug Luiz Capitulino
2015-02-26 19:26 ` [Qemu-devel] " Luiz Capitulino
2015-02-27 4:09 ` zhanghailiang
2015-02-27 4:09 ` [Qemu-devel] " zhanghailiang
2015-02-27 14:42 ` Luiz Capitulino
2015-02-27 14:42 ` [Qemu-devel] " Luiz Capitulino
2015-03-02 6:22 ` Amit Shah
2015-03-02 6:22 ` [Qemu-devel] " Amit Shah
2015-03-02 19:04 ` Luiz Capitulino [this message]
2015-03-02 19:04 ` Luiz Capitulino
2015-03-03 6:27 ` zhanghailiang
2015-03-03 6:27 ` [Qemu-devel] " zhanghailiang
2015-02-27 7:27 ` Markus Armbruster
2015-02-27 7:27 ` Markus Armbruster
2015-02-27 14:55 ` Luiz Capitulino
2015-02-27 14:55 ` Luiz Capitulino
[not found] ` <260321994.2482175.1425124149538.JavaMail.zimbra@oxygem.tv>
2015-02-28 11:50 ` Alexandre DERUMIER
2015-02-28 11:50 ` [Qemu-devel] " Alexandre DERUMIER
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=20150302140454.70a2006b@redhat.com \
--to=lcapitulino@redhat.com \
--cc=amit.shah@redhat.com \
--cc=eblake@redhat.com \
--cc=hangaohuai@huawei.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhang.zhanghailiang@huawei.com \
/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.