From: Kevin Wolf <mail@kevin-wolf.de>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] Machine config files
Date: Fri, 12 Jun 2009 16:22:16 +0200 [thread overview]
Message-ID: <4A326498.90801@kevin-wolf.de> (raw)
In-Reply-To: <87vdn11rzy.fsf@pike.pond.sub.org>
Markus Armbruster schrieb:
> Kevin Wolf <mail@kevin-wolf.de> writes:
>
>> Paul Brook schrieb:
>>> On Thursday 11 June 2009, Gerd Hoffmann wrote:
>>>> On 06/10/09 19:38, Paul Brook wrote:
>>>>> The following series implements machine config files, and adds converts
>>>>> some of the existing hardcoded machines.
>>>> Hmm. The converted machine types have a pretty static configuration,
>>>> i.e. where you don't need to specify more that just "-M type" on the
>>>> command line.
>>>>
>>>> What is the plan for machines which can be configured in alot of
>>>> different ways such as a typical PC? Where you can configure lots of
>>>> details such as cpu, memory, nic, disk drives, ... using command line
>>>> options?
>>> I don't believe most of these things should be configured by commandline
>>> options. It's only done that way because we don't have any alternative (i.e. a
>>> machine config file). If you really want full control, I expect your VM
>>> manager will generate the machine config for you.
>> >From my perspective as a qemu user, I definitely don't want to miss the
>> command line options. Not having to create configuration files is
>> exactly what gave me the "just works" feeling when I started using qemu.
>> And I really don't plan to use management tools in future.
>
> I understand where you come from. For me, configuration files are fine.
Don't get me wrong, I'm not against configuration files. Having them is
great and probably I'd even find some uses for them occasionally. I just
don't want to be _forced_ to use them which I fear is what Paul is
talking about.
> What I don't want is having to copy a lengthy configuration file just to
> add a device. Because that leads to zillions of copies with little
> differences here and there, and much diffing and merging on upgrade.
Sure, couldn't agree more, but this is a different story. The solution
for my problem is to retain command line options, the solution for your
problem is some mechanism to have a config that adds devices to an
existing base config (or changes options, removes devices, whatever).
Probably my command line switches would use the same mechanism
internally, but I don't really care. I'm just a random qemu user in this
discussion. ;-)
Kevin
next prev parent reply other threads:[~2009-06-12 14:23 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 17:38 [Qemu-devel] [PATCH 0/4] Machine config files Paul Brook
2009-06-10 17:38 ` [Qemu-devel] [PATCH 1/4] Include and build libfdt Paul Brook
2009-06-10 19:08 ` Glauber Costa
2009-06-10 19:23 ` Anthony Liguori
2009-06-10 19:27 ` Paul Brook
2009-06-10 19:41 ` Glauber Costa
2009-06-10 20:38 ` Paul Brook
2009-06-10 22:32 ` Edgar E. Iglesias
2009-06-10 19:34 ` Blue Swirl
2009-06-10 17:38 ` [Qemu-devel] [PATCH 2/4] Add device tree machine Paul Brook
2009-06-10 18:30 ` Blue Swirl
2009-06-10 19:10 ` Paul Brook
2009-06-11 13:22 ` Gerd Hoffmann
2009-06-11 13:33 ` Gerd Hoffmann
2009-06-11 13:39 ` Paul Brook
2009-06-11 14:22 ` Gerd Hoffmann
2009-06-12 16:25 ` Markus Armbruster
2009-06-10 17:38 ` [Qemu-devel] [PATCH 3/4] Stellaris machine config Paul Brook
2009-06-11 8:21 ` M P
2009-06-11 16:32 ` Jamie Lokier
2009-06-12 8:29 ` Gerd Hoffmann
2009-06-12 13:56 ` Markus Armbruster
2009-06-12 13:53 ` Markus Armbruster
2009-06-12 15:25 ` Jamie Lokier
2009-06-10 17:38 ` [Qemu-devel] [PATCH 4/4] Integrator " Paul Brook
2009-06-11 9:54 ` [Qemu-devel] [PATCH 0/4] Machine config files Gerd Hoffmann
2009-06-11 12:53 ` Gerd Hoffmann
2009-06-11 13:18 ` Paul Brook
2009-06-11 14:35 ` Gerd Hoffmann
2009-06-12 7:51 ` Kevin Wolf
2009-06-12 13:49 ` Markus Armbruster
2009-06-12 14:22 ` Kevin Wolf [this message]
2009-06-12 14:40 ` Markus Armbruster
2009-06-12 15:02 ` Anthony Liguori
2009-06-12 15:29 ` Kevin Wolf
2009-06-12 16:35 ` Blue Swirl
2009-06-12 13:37 ` Markus Armbruster
2009-06-12 14:44 ` Gerd Hoffmann
2009-06-12 15:58 ` Markus Armbruster
2009-06-12 16:11 ` [Qemu-devel] " Jan Kiszka
2009-07-06 12:49 ` Michael S. Tsirkin
2009-07-06 13:43 ` Gerd Hoffmann
2009-07-06 13:56 ` Michael S. Tsirkin
2009-07-06 14:01 ` Michael S. Tsirkin
2009-07-06 14:40 ` Gerd Hoffmann
2009-07-06 16:12 ` Avi Kivity
2009-07-06 16:27 ` Gerd Hoffmann
2009-07-06 16:37 ` Avi Kivity
2009-07-06 16:44 ` Michael S. Tsirkin
2009-07-07 4:47 ` Avi Kivity
2009-07-06 16:47 ` Paul Brook
2009-07-07 5:01 ` Avi Kivity
2009-07-06 17:28 ` Anthony Liguori
2009-07-06 22:39 ` Paul Brook
2009-07-06 23:13 ` Anthony Liguori
2009-07-07 5:00 ` Avi Kivity
2009-07-07 5:23 ` Avi Kivity
2009-07-07 4:56 ` Avi Kivity
2009-07-07 6:19 ` Michael S. Tsirkin
2009-07-06 14:24 ` Gerd Hoffmann
2009-07-06 14:31 ` Michael S. Tsirkin
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=4A326498.90801@kevin-wolf.de \
--to=mail@kevin-wolf.de \
--cc=armbru@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).