On Thu, Apr 25, 2019 at 08:07:06PM +0200, Philippe Mathieu-Daudé wrote: > On 1/4/19 4:16 PM, Peter Maydell wrote: > > On Thu, 3 Jan 2019 at 14:41, Stefan Hajnoczi <stefa...@redhat.com> wrote: > >> > >> This reverts commit 01fd41ab3fb69971c24a69ed49cde96086d81278. > >> > >> The generic loader device (-device loader,file=kernel.bin) can be used > >> to load a kernel instead of the -kernel option. Some boards have flash > >> memory (pflash) that is set via the -pflash or -drive options. > >> > >> Allow starting QEMU without the -kernel option to accommodate these > >> scenarios. > >> > >> Suggested-by: Peter Maydell <peter.mayd...@linaro.org> > >> Signed-off-by: Stefan Hajnoczi <stefa...@redhat.com> > > Previous to this commit (v3.1), we have: > > $ qemu-system-aarch64 -M netduino2 > qemu-system-aarch64: Guest image must be specified (using -kernel) > > Now (v4.0) we get: > > $ qemu-system-aarch64 -M netduino2 > qemu: fatal: Lockup: can't escalate 3 to HardFault (current priority -1)
A user-friendly error message is needed here. The check for -kernel was too specific and is not desirable for microbit where we use -device loader. Old boards probably want to continue using -kernel. New boards like microbit may use just -device loader. Perhaps there is even a group that wants both options. A solution is to introduce explicit checks so that we can tell the user the appropriate option for the machine type. I can work on this if you like, but probably won't be able to send a patch until Tuesday. Stefan
signature.asc
Description: PGP signature
