From: Paolo Bonzini <pbonzini@redhat.com>
To: Mario Smarduch <m.smarduch@samsung.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Cc: "christoffer.dall@linaro.org" <christoffer.dall@linaro.org>,
Marc Zyngier <Marc.Zyngier@arm.com>,
Gleb Natapov <gleb@kernel.org>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: maybe a virtio-balloon-device issue ?
Date: Fri, 06 Feb 2015 16:57:13 +0100 [thread overview]
Message-ID: <54D4E459.9040007@redhat.com> (raw)
In-Reply-To: <54D41681.7080401@samsung.com>
On 06/02/2015 02:18, Mario Smarduch wrote:
> Hi,
>
> I'm looking into qemu/balloon driver VM overcommit. I noticed
> virtio-balloon driver will take any setting from virtio-balloon-device
> to the point Guest dies.
>
> For a 1G guest
> $ sudo echo balloon 100 | socat - tcp4-connect:127.0.0.1:4444
>
> you get (same with libvirt setmem)
>
> root@localhost:~# free
> -bash: fork: Cannot allocate memory
> root@localhost:~# ps
> -bash: fork: Cannot allocate memory
>
> $ sudo info balloon | socat ... - confirms setting
>
> The balloon driver has been there for a while, not sure what I'm missing?
>
> virtio-balloon-device provide free memory, i.e., - externally accessible
> to host. But this appears more like a hint for an inflate request, snmp
> mibs
> provide more detailed resource info then that.
>
> I'm wondering if the driver should not have some heuristic
> check for an inflate request so it doesn't over inflate? Similar to
> kernel overcommit.
See this patch:
commit 5a10b7dbf904bfe01bb9fcc6298f7df09eed77d5
Author: Raushaniya Maksudova <rmaksudova@parallels.com>
Date: Mon Nov 10 09:36:29 2014 +1030
virtio_balloon: free some memory from balloon on OOM
Looks like the QEMU part was never posted though.
Paolo
next prev parent reply other threads:[~2015-02-06 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 1:18 maybe a virtio-balloon-device issue ? Mario Smarduch
2015-02-06 15:57 ` Paolo Bonzini [this message]
2015-02-09 17:38 ` Mario Smarduch
2015-02-20 2:46 ` Mario Smarduch
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=54D4E459.9040007@redhat.com \
--to=pbonzini@redhat.com \
--cc=Marc.Zyngier@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=m.smarduch@samsung.com \
--cc=peter.maydell@linaro.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.