From: Anthony Liguori <anthony@codemonkey.ws>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Amit Shah <amit.shah@redhat.com>,
chrisw@redhat.com, dlaor@redhat.com, avi@redhat.com,
rjones@redhat.com
Subject: Re: [Qemu-devel] Re: Machine-readable or parseable qemu output
Date: Thu, 15 Jan 2009 14:27:05 -0600 [thread overview]
Message-ID: <496F9C19.8020502@codemonkey.ws> (raw)
In-Reply-To: <20090114112317.GD24995@redhat.com>
Daniel P. Berrange wrote:
> On Wed, Jan 14, 2009 at 04:40:05PM +0530, Amit Shah wrote:
>
>> Hello,
>>
>> Continuing from the thread at [1], building on Daniel's suggestions, I
>> have jot down a few points as to how a libqemumonitor API could be
>> developed.
>>
>> To recap, there has to be an interface to the qemu monitor in
>> a way that wouldn't break even if the monitor output changes. This API
>> will remain the same, so that consumers (libvirt, etc) can safely
>> integrate with the monitor.
>>
>> Please see Dan's email at [1] to get the background details.
>>
>> [1] http://www.mail-archive.com/qemu-devel@nongnu.org/msg14615.html
>>
>> Here are some initial thoughts. Comments?
>>
>
> I'd like to add one more requirement
>
> - Works with existing QEMU monitor for releases >= 0.8.0
>
I think this is a bad requirement.
> This is because libvirt currently supports all QEMU >= 0.8.0,
libvirt has no bearing on upstream QEMU support :-)
> so if
> we're to be able to make use of this library we can't restrict it
> to just new releases.
But you can conditionally use the new library instead of your custom
parsing code for newer QEMU versions.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-01-15 20:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 11:10 [Qemu-devel] Machine-readable or parseable qemu output Amit Shah
2009-01-14 11:23 ` [Qemu-devel] " Daniel P. Berrange
2009-01-15 20:27 ` Anthony Liguori [this message]
2009-01-15 20:58 ` Daniel P. Berrange
2009-01-15 21:30 ` Anthony Liguori
2009-01-15 21:48 ` Avi Kivity
2009-01-15 22:26 ` Anthony Liguori
2009-01-14 11:28 ` Avi Kivity
2009-01-15 20:28 ` Anthony Liguori
2009-01-14 11:29 ` Richard W.M. Jones
2009-01-14 11:31 ` Avi Kivity
2009-01-14 11:36 ` Richard W.M. Jones
2009-01-14 11:45 ` Daniel P. Berrange
2009-01-14 12:37 ` Dor Laor
2009-01-14 14:05 ` Avi Kivity
2009-01-15 20:31 ` Anthony Liguori
2009-01-14 16:56 ` Jamie Lokier
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=496F9C19.8020502@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=amit.shah@redhat.com \
--cc=avi@redhat.com \
--cc=berrange@redhat.com \
--cc=chrisw@redhat.com \
--cc=dlaor@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.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.