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: Blue Swirl
Subject: Re: [Qemu-devel] For all targets and machine types: "start to monitor" smoke test
Date: Wed, 8 Aug 2012 19:34:51 +0000

On Wed, Aug 8, 2012 at 7:39 AM, Markus Armbruster <address@hidden> wrote:
> Blue Swirl <address@hidden> writes:
>
>> On Tue, Aug 7, 2012 at 7:26 PM, Markus Armbruster <address@hidden> wrote:
>>> Very basic smoke test: start QEMU with -monitor stdio, quit immediately.
>>> Wouldn't it be nice if that worked for all targets and machine types?
>>>
>>> Many targets have mandatory options (fun oxymoron), such as -kernel or
>>> -pflash.  Can't stop me, I just try a bunch until something works.
>>>
>>
>> Funny, I tried pretty similar stuff earlier but with qtest:
>> http://lists.nongnu.org/archive/html/qemu-devel/2012-04/msg01880.html
>
> I'd like to see such a test in "make check", too.
>
> I missed your try, or I forgot it since, thanks for the pointer.
>
> I'd prefer providing mocked up images for the test over disabling ROM
> and kernel loading in many places (your patch), let alone butchering it
> (my hackery; clearly not committable).

Fake files could work. Since qtest does not execute any code, any
ROMs, kernels or initrd files are somewhat useless. But since my
approach was not acceptable, I'll let the ARM etc. people solve the
need for those files how they want when they introduce qtests for
their devices.



reply via email to

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