Re: [Qemu-devel] [PATCH 0/4] Machine config files

[Markus Armbruster]

Kevin Wolf <address@hidden> writes:

> Markus Armbruster schrieb:
>> Kevin Wolf <address@hidden> 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

It is a different story, and I consider both stories valid.

> 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. ;-)

Yes, it would be nice if monitor commands, command line options and
configuration file directives to add devices were all frontends to the
same code.