From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Eric Blake <eblake@redhat.com>, Gerd Hoffman <kraxel@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH 0/9] qemu capabilities reporting and config changes
Date: Mon, 19 Mar 2012 17:33:50 +0100 [thread overview]
Message-ID: <4F675FEE.7020605@redhat.com> (raw)
In-Reply-To: <4F675F63.7070305@codemonkey.ws>
Il 19/03/2012 17:31, Anthony Liguori ha scritto:
>>> It also plumbs the existing command line options through QemuOpts via
>>> a special
>>> 'system' section. This means that any command line option can be
>>> specified via
>>> readconfig and that the combination of -nodefconfig and -writeconfig
>>> should give
>>> you exactly the same guest in a repeatable fashion.
>>
>> I don't like this because it turns command-line options into ABI.
>
> It's already an ABI, no?
Right, sorry. Into configuration file ABI, which is supposed to be the
"cleaner" ABI.
>> Also, it puts there some options for which -writeconfig is actually
>> able to produce a QemuOpts equivalent, such as -monitor.
>
> That may be a bug depending on what your concern is. Can you be more
> specific?
If you write "-monitor stdio" with your series, do you get one or two
monitors in the resulting configuration file?
Paolo
next prev parent reply other threads:[~2012-03-19 16:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 15:09 [Qemu-devel] [RFC PATCH 0/9] qemu capabilities reporting and config changes Anthony Liguori
2012-03-19 15:09 ` [Qemu-devel] [PATCH 1/9] qemu-config: fix -writeconfig when using qemu_opt_set_bool Anthony Liguori
2012-03-19 15:09 ` [Qemu-devel] [PATCH 2/9] qemu-config: friends don't let friends use sscanf Anthony Liguori
2012-03-19 15:09 ` [Qemu-devel] [PATCH 3/9] vl: refactor command line parsing to allow options to be set via config Anthony Liguori
2012-03-19 15:09 ` [Qemu-devel] [PATCH 4/9] vl: mark system configuration options in qemu-options.hx Anthony Liguori
2012-03-19 15:09 ` [Qemu-devel] [PATCH 5/9] vl: enable system configuration to be used Anthony Liguori
2012-03-19 15:09 ` [Qemu-devel] [PATCH 6/9] vl: parse all options via QemuOpts Anthony Liguori
2012-03-19 15:09 ` [Qemu-devel] [PATCH 7/9] qmp: expose a command to query capabilities of config parser Anthony Liguori
2012-03-19 20:10 ` Eric Blake
2012-03-19 20:19 ` Anthony Liguori
2012-03-19 20:31 ` Eric Blake
2012-03-19 20:41 ` Anthony Liguori
2012-03-19 15:09 ` [Qemu-devel] [PATCH 8/9] vl: add -query-capabilities Anthony Liguori
2012-03-20 7:49 ` Gerd Hoffmann
2012-03-20 10:33 ` Daniel P. Berrange
2012-03-20 19:39 ` Eduardo Habkost
2012-03-19 15:09 ` [Qemu-devel] [PATCH 9/9] Add a management tool writer's guide Anthony Liguori
2012-03-19 16:09 ` [Qemu-devel] [RFC PATCH 0/9] qemu capabilities reporting and config changes Paolo Bonzini
2012-03-19 16:31 ` Anthony Liguori
2012-03-19 16:33 ` Paolo Bonzini [this message]
2012-03-19 16:41 ` Anthony Liguori
2012-03-19 16:45 ` Paolo Bonzini
2012-03-19 16:53 ` Anthony Liguori
2012-03-19 17:03 ` Paolo Bonzini
2012-03-20 7:54 ` Gerd Hoffmann
2012-03-20 19:47 ` Eduardo Habkost
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=4F675FEE.7020605@redhat.com \
--to=pbonzini@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kraxel@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 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.