From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Mark Burton <mark.burton@greensocs.com>
Cc: "Damien Hedde" <damien.hedde@greensocs.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
"Markus Armbruster" <armbru@redhat.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Mirela Grujic" <mirela.grujic@greensocs.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: Redesign of QEMU startup & initial configuration
Date: Thu, 9 Dec 2021 20:28:03 +0000 [thread overview]
Message-ID: <YbJm0+gK/iLsaBsb@redhat.com> (raw)
In-Reply-To: <CE6F7A66-A5B9-45CA-9E9D-C8AFFB2976D5@greensocs.com>
On Thu, Dec 09, 2021 at 09:01:24PM +0100, Mark Burton wrote:
> I’ll take the liberty to cut one part (I agree with much of what you say elsewhere)
>
> > On 9 Dec 2021, at 20:11, Daniel P. Berrangé <berrange@redhat.com> wrote:
> >
> > As illustrated earlier, I'd really like us to consider being a bit
> > more adventurous on the CLI side. I'm convinced that a CLI for
> > directly configurable hardware is doomed to be horrible no matter
> > what, if you try to directly expose all QAPI configuration
> > flexibilty. Whether key/value, JSON, whatever, it will become
> > unmanagable on the CLI because VM hardware config is inherantly
> > complicated.
> >
>
> I absolutely agree, but reach a slightly different conclusion
>
> > Thus my though that config files or QMP should be the only two
> > places where the full power of QAPI config is exposed. Use CLI
> > as just a way to interact with config files in a simple way
> > with templates.
>
> I would countenance that we choose only one place to ‘support’ an interface. Either “Yet Another Hardware Configuration Language” or QAPI. Rather than re-inventing that wheel I would simply suggest that we leave that to the relevant ‘user’ community (libvirt, whatever), who have specific requirements and/or existing solutions. Leaving QEMU itself to focus on improving QAPI (and migrating the CLI).
Yes, indeed, the logical extension of my idea is that the 'simple'
CLI + templating thing doesn't atually have to be in the main QEMU
binary at all. We could in fact ship a bare '/usr/bin/qemu' which
does the config file templating and spawns whatever full QEMU
binary (/usr/bin/qemu-system-blah) does the real VM. The key is
just that we have something simple for users, who don't want a
full mgmt layer and like the historical QEMU simple configs.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-12-09 20:29 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 6:57 Redesign of QEMU startup & initial configuration Markus Armbruster
2021-12-09 19:11 ` Daniel P. Berrangé
2021-12-09 20:01 ` Mark Burton
2021-12-09 20:28 ` Daniel P. Berrangé [this message]
2021-12-10 8:34 ` Paolo Bonzini
2021-12-10 11:25 ` Daniel P. Berrangé
2021-12-10 14:15 ` Mark Burton
2021-12-10 14:26 ` Daniel P. Berrangé
2021-12-10 14:42 ` Mark Burton
2021-12-10 15:13 ` Paolo Bonzini
2021-12-10 15:26 ` Markus Armbruster
2021-12-10 15:39 ` Daniel P. Berrangé
2021-12-13 15:19 ` Markus Armbruster
2021-12-13 17:30 ` Paolo Bonzini
2021-12-13 17:59 ` Daniel P. Berrangé
2021-12-13 20:22 ` Mark Burton
2021-12-14 13:05 ` Daniel P. Berrangé
2021-12-14 13:11 ` Mark Burton
2021-12-14 13:21 ` Daniel P. Berrangé
2021-12-14 13:36 ` Mark Burton
2021-12-14 13:48 ` Daniel P. Berrangé
2021-12-14 14:42 ` Mark Burton
2021-12-14 14:56 ` Daniel P. Berrangé
2021-12-14 15:12 ` Markus Armbruster
2021-12-14 15:14 ` Mark Burton
2021-12-10 13:54 ` Markus Armbruster
2021-12-10 15:38 ` Paolo Bonzini
2021-12-13 15:28 ` Markus Armbruster
2021-12-13 17:37 ` Paolo Bonzini
2021-12-13 18:07 ` Daniel P. Berrangé
2021-12-13 18:37 ` Paolo Bonzini
2021-12-13 18:53 ` Daniel P. Berrangé
2021-12-14 7:09 ` Meeting today? Mark Burton
2021-12-14 11:37 ` Markus Armbruster
2021-12-14 11:39 ` Mark Burton
2021-12-14 12:49 ` Daniel P. Berrangé
2021-12-14 14:49 ` Markus Armbruster
2022-01-04 9:29 ` Edgar E. Iglesias
2022-01-06 11:21 ` "Startup" meeting (was Re: Meeting today?) Mark Burton
2022-01-06 11:23 ` Daniel P. Berrangé
2022-01-11 10:20 ` Philippe Mathieu-Daudé
2022-01-11 10:22 ` Mark Burton
2022-01-17 17:13 ` Kevin Wolf
2022-01-17 19:02 ` Markus Armbruster
2022-01-23 20:49 ` Mark Burton
2022-01-25 8:50 ` Juan Quintela
2022-01-25 10:45 ` Philippe Mathieu-Daudé via
2022-01-25 10:58 ` Juan Quintela
2022-02-08 11:52 ` Mark Burton
2022-02-08 12:35 ` Juan Quintela
2022-01-11 10:28 ` Daniel P. Berrangé
2021-12-15 18:46 ` Redesign of QEMU startup & initial configuration Paolo Bonzini
2021-12-15 18:50 ` Daniel P. Berrangé
2021-12-14 11:48 ` Markus Armbruster
2021-12-14 13:00 ` Mark Burton
2021-12-14 14:54 ` Markus Armbruster
2021-12-15 20:00 ` Paolo Bonzini
2021-12-15 20:14 ` Mark Burton
2021-12-16 10:24 ` Markus Armbruster
2021-12-16 15:28 ` Paolo Bonzini
2021-12-16 15:40 ` Daniel P. Berrangé
2021-12-16 16:00 ` Mark Burton
2021-12-16 16:15 ` Daniel P. Berrangé
2021-12-16 16:27 ` Mark Burton
2021-12-13 10:51 ` Damien Hedde
2021-12-13 15:47 ` Markus Armbruster
2022-01-04 12:40 ` Richard W.M. Jones
2022-01-13 16:10 ` Markus Armbruster
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=YbJm0+gK/iLsaBsb@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=damien.hedde@greensocs.com \
--cc=edgar.iglesias@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=mark.burton@greensocs.com \
--cc=mirela.grujic@greensocs.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 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.