From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Connor Kuehl <ckuehl@redhat.com>
Cc: jejb@linux.ibm.com, npmccallum@redhat.com, qemu-devel@nongnu.org,
dgilbert@redhat.com
Subject: Re: Interactive launch over QMP socket?
Date: Mon, 22 Feb 2021 15:36:25 +0000 [thread overview]
Message-ID: <YDPPeVXzcttsJsJU@redhat.com> (raw)
In-Reply-To: <d137b4ee-7dbe-6bd5-63c9-b20a80259d08@redhat.com>
On Mon, Feb 22, 2021 at 09:00:36AM -0600, Connor Kuehl wrote:
> On 2/22/21 6:18 AM, Daniel P. Berrangé wrote:
> >
> > ... so this doesn't actually seem to need to be done in QMP on the fly.
> > It can be provided on the CLI, which seems to be possible wth the args
> > shown earlier.
> >
>
> >
> > It seems like this is all doable already unless I'm missing something.
>
> That's correct; however, I would like to make it possible for the entirety
> of it to happen on the fly, ultimately rendering the CLI args optional.
There is a long term goal to make entire of QEMU CLI optional, such that
it only contains the QMP config, and then do every thing related to VM
setup as QMP commands. So if current CLI is functionally sufficient,
then eventually, the same will be doable exclusively at runtime. We
don't have a firm ETA for this though.
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 :|
prev parent reply other threads:[~2021-02-22 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 18:01 Interactive launch over QMP socket? Connor Kuehl
2021-02-10 18:14 ` James Bottomley
2021-02-10 18:46 ` Connor Kuehl
2021-02-10 19:06 ` James Bottomley
2021-02-10 20:39 ` Connor Kuehl
2021-02-11 9:11 ` Dr. David Alan Gilbert
2021-02-22 11:40 ` Kevin Wolf
2021-02-22 15:39 ` Daniel P. Berrangé
2021-02-22 16:23 ` Kevin Wolf
2021-02-22 12:18 ` Daniel P. Berrangé
2021-02-22 15:00 ` Connor Kuehl
2021-02-22 15:36 ` Daniel P. Berrangé [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=YDPPeVXzcttsJsJU@redhat.com \
--to=berrange@redhat.com \
--cc=ckuehl@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jejb@linux.ibm.com \
--cc=npmccallum@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).