qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kashyap Chamarthy <kchamart@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Damien Hedde <damien.hedde@greensocs.com>,
	peter.maydell@linaro.org, richard.fuhler@sifive.com,
	sam.grove@sifive.com, Mark Burton <mark.burton@greensocs.com>,
	armbru@redhat.com, qemu-devel@nongnu.org,
	edgar.iglesias@gmail.com, Luc Michel <luc.michel@greensocs.com>,
	f4bug@amsat.org
Subject: Re: About creating machines on the command line
Date: Thu, 14 Jan 2021 18:11:50 +0100	[thread overview]
Message-ID: <20210114171150.GA94798@paraplu.home> (raw)
In-Reply-To: <20210114113706.GF1643043@redhat.com>

On Thu, Jan 14, 2021 at 11:37:06AM +0000, Daniel P. Berrangé wrote:
> On Mon, Jan 11, 2021 at 03:50:58PM +0100, Luc Michel wrote:

[...]

> > This would hopefully allow for simple machines creation. We would then be
> > able to use either the command line or the `-readconfig` option to create
> > the machine.
> > 
> > Note that we are not planning to use QMP/HMP for now. From our
> > understanding, a `device_add` request is always considered as hot-plug,
> > which is not what we want here.
> > 
> > Please tell us what do you think about this plan. Any feedback is
> > appreciated.  Then we can discuss the details of how to do this properly.
> 
> There's a general desire amongst QEMU maintainers to move to a world
> where QAPI is used for describing everything. In this vision, eventually
> all current command line options would be replaced with QMP commands
> and QAPI objects specs.
> 
> In this world -readconfig is likely to be deleted. 

In that case, I hope the above intention / direction will be documented
somewhere more clearly.  In the past I ran into at least a couple of
companies that use QEMU in production and heavily rely on '-readconfig',
despite knowing some of its shortcomings.  There might be others out
there.

> Also this means we have a bias against adding new command line options
> to current QEMU.

[...]

-- 
/kashyap



  reply	other threads:[~2021-01-14 18:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 14:50 About creating machines on the command line Luc Michel
2021-01-11 20:04 ` BALATON Zoltan
2021-01-11 20:28   ` Liviu Ionescu
2021-01-14 10:56     ` Luc Michel
2021-01-14 11:07       ` Liviu Ionescu
2021-01-14  9:30   ` Luc Michel
2021-01-14 11:37 ` Daniel P. Berrangé
2021-01-14 17:11   ` Kashyap Chamarthy [this message]
2021-01-14 17:26     ` Daniel P. Berrangé
2021-02-03 16:55 ` Philippe Mathieu-Daudé
2021-02-03 17:09   ` graf--- via
2021-02-04 20:29     ` John Snow
2021-02-05 16:04       ` Luc Michel
2021-02-05 10:43     ` Luc Michel
2021-02-10 12:13       ` Alexander Graf
2021-02-13 13:58         ` Luc Michel

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=20210114171150.GA94798@paraplu.home \
    --to=kchamart@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=damien.hedde@greensocs.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=f4bug@amsat.org \
    --cc=luc.michel@greensocs.com \
    --cc=mark.burton@greensocs.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.fuhler@sifive.com \
    --cc=sam.grove@sifive.com \
    /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).