None of QEMU's ARM boards automatically boot a bios image shipped with
QEMU. You must provide one explicitly, or else use the 'built in
bootloader" with -kernel. (I'm not aware of any rom image that would
work on QEMU versatilepb and load a kernel off a disk image, so in
practice -kernel is what yo
As a sidenote: may I ask why the given command does not work? The IMG
should contain a kernel that should be bootable, so there should be no
need to specify an extra kernel.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs
No problem -- QEMU is unfortunately not as clear as it perhaps could be
about what happens in this situation.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.ne
Oh right, stupid mistake then! Never mind. Thanks for pointing this out.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1500175
Title:
unable to init msix vectors
Status in QEMU:
New
Bug descrip
The "unable to init msix vectors" message is just a warning, and is
harmless -- it is expected for the ARM boards. (There's a patch around
that suppresses the incorrect warning but unfortunately it didn't get
into 2.4.)
Your actual problem is that you haven't specified either a guest kernel
(via -
