Re: [Qemu-devel] For all targets and machine types: "start to monitor" smoke test

[Markus Armbruster]

Peter Maydell <address@hidden> writes:

> On 8 August 2012 08:50, Markus Armbruster <address@hidden> wrote:
>> Markus Armbruster <address@hidden> writes:
>>> The string should be suitable for inserting into -help.
>>
>> Sufficiently common cases can also be delegated to generic code:
>>
>> * Maximum number of CPUs
>>
>>   Got that: QEMUMachine member max_cpus, main() enforces it.
>>
>> * Require -kernel
>>
>>   Have a flag in QEMUMachine, enforce in main().
>>
>> * Require certain drives
>>
>>   Have QEMUMachine declare minimum and maximum number drives of each
>>   BlockInterfaceType?
>
> I'm not entirely sure what the aim here is? Allow some automated test
> program to programmatically determine required arguments for a
> smoke test? Make machines consistent about how they inform the
> user about required arguments etc? Let us print this info in --help?
> Something else?

I think each of the above would be nice to have, no more, no less.