From: Eric Blake <eblake@redhat.com>
To: Yonit Halperin <yhalperi@redhat.com>
Cc: mprivozn@redhat.com, qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH] spice: increase the verbosity of spice section in "qemu --help"
Date: Mon, 27 Aug 2012 08:56:00 -0600 [thread overview]
Message-ID: <503B8A80.4080801@redhat.com> (raw)
In-Reply-To: <5039C456.6020301@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
On 08/26/2012 12:38 AM, Yonit Halperin wrote:
> On 08/21/2012 03:31 PM, Eric Blake wrote:
>> On 08/21/2012 04:54 AM, Yonit Halperin wrote:
>>> Added all spice options to the help string. This can be used by libvirt
>>> to determine which spice related features are supported by qemu.
>>
>> For older released, this is true; but for future versions of qemu,
>> libvirt would much rather learn this information from QMP commands than
>> from scraping -help output. Can we get at all of this information
>> from QMP?
>>
> No, we don't have qmp commands for any of spice config options. I don't
> think it should be in the scope of this patch.
But since we have already declared that 1.2 is the last release where
libvirt will be scraping -help output, and that 1.3 and later will allow
libvirt to query all configuration information via QMP commands, I think
that you really _do_ need to consider QMP commands in the scope of this
patch series, if you expect libvirt to be able to react to this
information in qemu 1.3.
--
Eric Blake eblake@redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
prev parent reply other threads:[~2012-08-27 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 10:54 [Qemu-devel] [PATCH] spice: increase the verbosity of spice section in "qemu --help" Yonit Halperin
2012-08-21 11:06 ` Gerd Hoffmann
2012-08-21 12:31 ` Eric Blake
2012-08-26 6:38 ` Yonit Halperin
2012-08-27 14:56 ` Eric Blake [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=503B8A80.4080801@redhat.com \
--to=eblake@redhat.com \
--cc=kraxel@redhat.com \
--cc=mprivozn@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yhalperi@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.