[Qemu-devel] unicore32 fails assertion without -kernel (was: How to reliably start a bare QEMU target to query capabilities via QMP)

[Markus Armbruster <armbru@redhat.com>]

"Daniel P. Berrange" <berrange@redhat.com> writes:

> I've been adapting libvirt to use to the various new QMP commands to
> query QEMU's capabilities, instead of the hated -help parsing. Obviously
> the critical part of this is being able to reliably start a bare QEMU
> process with no actual guest OS configured (no disks, no kernel, etc)
> and talk to its monitor. I hadn't anticipated problems since I only
> tested with x86_64 / i386 most of the time, which work well in this
> respect. Currently I am doing
>
>   # $QEMU_BINARY -S \
>          -no-user-config \
>          -nodefconfig \
>          -nodefaults \
>          -nographic \
>          -qmp stdio
>
>
> This works for about 50% of the QEMU targets:
[...]
>  but fails for the other 50% of targets:
[...]
> With the failing targets i see the following kinds of errors:
>
>
>  $ qemu-system-arm -S -nodefconfig -nodefaults -nographic -qmp unix:/tmp/foo,server,nowait
>  Kernel image must be specified
[...]
>  $ qemu-system-unicore32 -S -nodefconfig -nodefaults -nographic -qmp unix:/tmp/foo,server,nowait
>  qemu-system-unicore32: /home/berrange/src/virt/qemu/hw/unicore32/../puv3.c:81: puv3_load_kernel: Assertion `kernel_filename != ((void *)0)' failed.
>  Aborted

Bug, cc'ing maintainer.  It should fail cleanly, like the test case
above.

A similar bug was recently fixed for armv7m (commit 01fd41ab).

[...]