From: Gerd Hoffmann <kraxel@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
MkfsSion <mkfssion@mkfssion.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] vl: Add -set options to device opts dict when using JSON syntax for -device
Date: Wed, 22 Dec 2021 09:22:47 +0100 [thread overview]
Message-ID: <20211222082247.epv27gxeq622d2ts@sirius.home.kraxel.org> (raw)
In-Reply-To: <871r26ge4z.fsf@dusky.pond.sub.org>
On Tue, Dec 21, 2021 at 04:40:28PM +0100, Markus Armbruster wrote:
> Paolo Bonzini <pbonzini@redhat.com> writes:
>
> > On 12/21/21 13:58, Markus Armbruster wrote:
> >>> Is this a regression? I suspect commit 5dacda5167 "vl: Enable JSON
> >>> syntax for -device" (v6.2.0).
> >>
> >> Obviously not a regression: everything that used to work still works.
> >
> > FWIW I think -set should be deprecated. I'm not aware of any
> > particularly useful use of it. There are a couple in the QEMU tests
> > (in vhost-user-test and in qemu-iotests 068), but in both cases the
> > code would be easier to follow without; patches can be dusted off if
> > desired.
>
> -set has its uses, but they're kind of obscure. When you want to use
> some canned configuration with slight modifications, then -readconfig
> canned.cfg -set ... is nicer than editing a copy of canned.cfg.
Simliar: configure stuff not supported by libvirt:
<qemu:commandline>
<qemu:arg value='-set'/>
<qemu:arg value='device.video0.guestdebug=1'/>
</qemu:commandline>
There will always be a gap between qemu and libvirt, even if most of
them are temporary only (while developing a new feature). I think we
need some way to deal with this kind of tweaks when moving to QAPI-based
machine setup. Possibly not in qemu, maybe it's easier to add new
'<qemu:set device=... property=... value=...>' syntax to libvirt.
take care,
Gerd
next prev parent reply other threads:[~2021-12-22 8:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 7:18 [PATCH] vl: Add -set options to device opts dict when using JSON syntax for -device MkfsSion
2021-12-21 11:26 ` Markus Armbruster
2021-12-21 12:58 ` Markus Armbruster
2021-12-21 14:47 ` Paolo Bonzini
2021-12-21 15:40 ` Markus Armbruster
2021-12-21 17:20 ` Damien Hedde
2021-12-21 17:31 ` Damien Hedde
2021-12-22 8:22 ` Gerd Hoffmann [this message]
2021-12-22 9:37 ` Damien Hedde
2021-12-22 10:47 ` Gerd Hoffmann
2022-01-04 13:14 ` Daniel P. Berrangé
2021-12-22 5:54 ` MkfsSion
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=20211222082247.epv27gxeq622d2ts@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mkfssion@mkfssion.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).