From: Luiz Capitulino <lcapitulino@redhat.com>
To: Saptarshi Sen <saptarshi.mrg@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Virtio-Balloon : config_set_size
Date: Thu, 20 Jun 2013 13:53:39 -0400 [thread overview]
Message-ID: <20130620135339.392a4632@redhat.com> (raw)
In-Reply-To: <CAG5Np+pBW0ni85+w=vyEJMOnxcBzkUnaEtVx53W19aj4LK6vbA@mail.gmail.com>
On Thu, 20 Jun 2013 12:49:17 +0800
Saptarshi Sen <saptarshi.mrg@gmail.com> wrote:
> Hi all,
>
> I am experimenting with the Virtio- balloon driver in qemu.
>
> When I set the balloon size to a arbitrary low value. I see
> the actual value of the balloon set is not what I intended
> but to a level probably decided by the system.
A few things might be happening there. Maybe the guest is just slow
and is still inflating the balloon when you type 'info balloon'. Or
the guest may be running out of memory and is temporarily unable to
keep inflating the balloon. Finally, if the guest runs out of memory
(because you inflated too much) it may OOPs and then you won't see
any balloon activity anymore.
> I am not able to explain this part who decides on the final
> size of the balloon.
>
> Another observation each time I do a qmp request to deflate the balloon
> the in the virtio-balloon.c config_set_size function is called. I do not
> understand who calls it and the method of activation
There's no such function in virtio-balloon.c, at least not in latest
git HEAD. Are you referring to virtio_balloon_set_config()? This function
is called when the virtio balloon driver in the guest wants to update
the balloon size.
prev parent reply other threads:[~2013-06-20 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 4:49 [Qemu-devel] Virtio-Balloon : config_set_size Saptarshi Sen
2013-06-20 17:53 ` Luiz Capitulino [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=20130620135339.392a4632@redhat.com \
--to=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=saptarshi.mrg@gmail.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 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).