From: Jan Kiszka <jan.kiszka@siemens.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Ian Campbell <Ian.Campbell@eu.citrix.com>,
Anthony Liguori <aliguori@us.ibm.com>,
"Richard W.M. Jones" <rjones@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RESEND][PATCH v3] Generalize -machine command line option
Date: Mon, 25 Jul 2011 13:48:17 +0200 [thread overview]
Message-ID: <4E2D5801.9020904@siemens.com> (raw)
In-Reply-To: <m3tyaa612s.fsf@blackfin.pond.sub.org>
On 2011-07-25 13:39, Markus Armbruster wrote:
> Jan Kiszka <jan.kiszka@siemens.com> writes:
>
>> On 2011-07-25 12:45, Richard W.M. Jones wrote:
>>> On Mon, Jul 25, 2011 at 12:33:01PM +0200, Jan Kiszka wrote:
>>>> On 2011-07-25 11:41, Richard W.M. Jones wrote:
>>>>> On Sat, Jul 23, 2011 at 12:38:37PM +0200, Jan Kiszka wrote:
>>>>>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>>>>>
>>>>>> -machine somehow suggests that it selects the machine, but it doesn't.
>>>>>> Fix that before this command is set in stone.
>>>>>>
>>>>>> Actually, -machine should supersede -M and allow to introduce arbitrary
>>>>>> per-machine options to the command line. That will change the internal
>>>>>> realization again, but we will be able to keep the user interface
>>>>>> stable.
>>>>>
>>>>> This breaks libguestfs which was doing:
>>>>>
>>>>> qemu -machine accel=kvm:tcg ...
>>>>>
>>>>> We are not passing any -M option at all. We don't particularly care
>>>>> about the machine type since we're not that performance sensitive and
>>>>> we don't need to serialize the machine state.
>>>>>
>>>>> I have checked, and this works:
>>>>>
>>>>> qemu -machine pc,accel=kvm:tcg ...
>>>>>
>>>>> "pc" is the default, right? What about for other architectures?
>>>>
>>>> Yes, pc is the right default. Other arch have other defaults.
>>>
>>> So what you're saying is we have to parse qemu -machine \? output by
>>> looking for the string '(default)'? eg:
>>>
>>> $ ./arm-softmmu/qemu-system-arm -machine \?|fgrep '(default)'
>>> integratorcp ARM Integrator/CP (ARM926EJ-S) (default)
>>>
>>> $ ./i386-softmmu/qemu -machine \?|fgrep '(default)'
>>> pc-0.14 Standard PC (default)
>>
>> I understand, this is clumsy. Will see if we can do better.
>
> Is there a technical reason why type isn't optional with -machine?
>
> [...]
Maybe it's just the
assert(!permit_abbrev || list->implied_opt_name);
in qemu_opts_parse, but I haven't looked at all details (and all other
users) yet.
>From -machine POV, I see no reason that prevents defaulting to some
machine type if "[type=]XXX" is missing in the command line.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-07-25 11:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 10:38 [Qemu-devel] [RESEND][PATCH v3] Generalize -machine command line option Jan Kiszka
2011-07-23 10:39 ` [Qemu-devel] [RESEND][PATCH 2/2] Deprecate -M command line options Jan Kiszka
2011-07-23 15:43 ` [Qemu-devel] [RESEND][PATCH v3] Generalize -machine command line option Anthony Liguori
2011-07-25 9:41 ` Richard W.M. Jones
2011-07-25 10:33 ` Jan Kiszka
2011-07-25 10:45 ` Richard W.M. Jones
2011-07-25 10:59 ` Jan Kiszka
2011-07-25 11:39 ` Markus Armbruster
2011-07-25 11:48 ` Jan Kiszka [this message]
2011-07-25 16:11 ` [Qemu-devel] [PATCH] Allow to leave type on default in -machine Jan Kiszka
2011-07-25 16:21 ` Richard W.M. Jones
2011-07-25 16:33 ` Alexander Graf
2011-07-29 14:37 ` Anthony Liguori
2011-07-25 12:23 ` [Qemu-devel] [RESEND][PATCH v3] Generalize -machine command line option Anthony Liguori
2011-07-25 11:48 ` Peter Maydell
2011-07-25 12:05 ` Peter Maydell
2011-07-25 12:18 ` Jan Kiszka
2011-07-25 12:22 ` Peter Maydell
2011-07-25 12:27 ` Jan Kiszka
2011-07-25 12:44 ` Alexander Graf
2011-07-25 12:47 ` Anthony Liguori
2011-07-25 12:49 ` Richard W.M. Jones
2011-07-25 12:53 ` Alexander Graf
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=4E2D5801.9020904@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=aliguori@us.ibm.com \
--cc=anthony.perard@citrix.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.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 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.