qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Markus Armbruster
Subject: Re: [Qemu-devel] For all targets and machine types: "start to monitor" smoke test
Date: Wed, 08 Aug 2012 09:50:26 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (gnu/linux)

Markus Armbruster <address@hidden> writes:

> Peter Maydell <address@hidden> writes:
>
>> On 7 August 2012 20:55, Markus Armbruster <address@hidden> wrote:
>>> Anthony Liguori <address@hidden> writes:
>>>> Perhaps we could add a QEMUMachine parameter that indicates that the
>>>> machine doesn't start without special options.
>>>
>>> Recommend to make it a string that lists the mandatory options.
>>
>> How are you going to say "need either option foo or option bar" ? I'm
>> pretty sure we have some of those (eg "either you need to pass a flash
>> image or a kernel").
>
> Yes, we do.
>
> 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?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]