qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org,
	mdroth@linux.vnet.ibm.com, jyang@redhat.com,
	lcapitulino@redhat.com, Amos Kong <akong@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] monitor: introduce query-config-schema
Date: Mon, 22 Apr 2013 09:00:05 -0600	[thread overview]
Message-ID: <51755075.1000008@redhat.com> (raw)
In-Reply-To: <517527FC.2090808@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]

On 04/22/2013 06:07 AM, Paolo Bonzini wrote:
> Il 22/04/2013 13:48, Amos Kong ha scritto:
>>>>>> Libvirt doesn't have a stable way to know option support
>>>>>> detail. This patch introdued a new qmp command to query
>>>>>> configuration schema information. hmp command isn't added.
>>>>
>>>> Can you introspect QemuOpts instead?  All new options are added there.
>>
>> It would be exact to use QemuOpts. I tried to output the vm_config_groups[]
>> in qemu-config.c, but it seems not enough. (desc list of -netdev, -drive,
>> -device are all empty)
> 
> That's expected because they are parsed otherwise, depending on the
> backend type.  -chardev is currently working but it's an implementation
> detail.

Libvirt cares most about newly added options, which should use qemuOpts
all the way.  We can understand that legacy options like -netdev might
not yet use qemuOpts, but they are also legacy options, and therefore
libvirt can already assume they exist since at least qemu 1.3 (when
libvirt switched over to QMP probing).  If we later add a new feature to
-netdev, we should also convert -netdev to qemuOpts at that time, so
that libvirt would know whether the new feature is available.

At any rate, we really DO want introspection, and having it in 1.5 is a
worthwhile goal.  Even if the introspection turns up empty on legacy
options, having it for the sake of new options is worth the effort.

-- 
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: 621 bytes --]

  reply	other threads:[~2013-04-22 15:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19  9:52 [Qemu-devel] [PATCH] monitor: introduce query-config-schema Amos Kong
2013-04-19 12:02 ` Osier Yang
2013-04-19 12:22   ` Eric Blake
2013-04-19 13:44   ` Osier Yang
2013-04-19 12:39 ` Eric Blake
2013-04-19 13:50   ` Osier Yang
2013-04-19 15:21 ` Paolo Bonzini
2013-04-22 11:48   ` Amos Kong
2013-04-22 12:07     ` Paolo Bonzini
2013-04-22 15:00       ` Eric Blake [this message]
2013-04-22 15:16         ` Paolo Bonzini
2013-04-23  2:40           ` Amos Kong
2013-04-23 13:20         ` Luiz Capitulino
2013-04-23 15:32           ` Eric Blake
2013-04-23 16:55             ` Luiz Capitulino

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=51755075.1000008@redhat.com \
    --to=eblake@redhat.com \
    --cc=akong@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=jyang@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=pbonzini@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).