qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Adam Litke <agl@us.ibm.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: libvir-list@redhat.com, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [libvirt] [PATCH] qemu: Get memory balloon info correctly for text monitor
Date: Mon, 15 Aug 2011 12:14:57 -0500	[thread overview]
Message-ID: <4E495411.1030905@us.ibm.com> (raw)
In-Reply-To: <20110815165042.GD24615@redhat.com>



On 08/15/2011 11:50 AM, Daniel P. Berrange wrote:
> On Mon, Aug 15, 2011 at 11:27:43AM -0500, Adam Litke wrote:
>> On 08/15/2011 08:23 AM, Osier Yang wrote:
>>> 于 2011年08月15日 21:58, Osier Yang 写道:
>>>> * src/qemu/qemu_monitor_text.c: BALLOON_PREFIX was defined as
>>>> "balloon: actual=", which cause "actual=" is stripped early before
>>>> the real parsing. This patch changes BALLOON_PREFIX into "balloon: ",
>>>> and modifies related functions, also renames
>>>> "qemuMonitorParseExtraBalloonInfo" to "qemuMonitorParseBalloonInfo",
>>>> as after the changing, it parses all the info returned by "info balloon".
>>>
>>> Forgot to mention the problem, e.g. "virsh dommemstat $domain" returns empty
>>> result.
>>
>> That is because qemu has disabled stats reporting and so the extra
>> fields are not present in the info balloon response.
> 
> I'd completely forgotten about this problem. We really should try to
> get this fixed & renabled in QEMU sometime in the not too distant
> future.

I agree.  The problem is that qemu lacks a proper interface for
asynchronous commands so an unresponsive guest could freeze the monitor.
 QMP is undergoing a significant overhaul as a result of the new QAPI
framework.  It is my understanding that this new framework will provide
a robust async interface, allowing us to re-enable balloon stats.

-- 
Adam Litke
IBM Linux Technology Center

           reply	other threads:[~2011-08-15 17:16 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20110815165042.GD24615@redhat.com>]

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=4E495411.1030905@us.ibm.com \
    --to=agl@us.ibm.com \
    --cc=berrange@redhat.com \
    --cc=libvir-list@redhat.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).