Hi Ben,
I found that "qemu-system-arm -machine raspi0",
u-boot-rpi:armel and linux-image-rpi do not seem bootable.
Specifically, I did the following (qemu-system-arm is from Sid):
qemu-system-arm -machine raspi0,firmware=/usr/lib/u-boot/rpi_0_w/u-boot.bin \
-display gtk -sd disk-image.qcow2
In "disk-image.qcow2", linux-image-rpi and u-boot-menu are installed.
"u-boot-rpi:armel" is installed only on a host.
u-boot-menu is used for only generating /boot/extlinux/extlinux.conf in the
guest.
In the guest "u-boot-update" command created the following
/boot/extlinux/extlinux.conf:
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 5
label l0
menu label Debian GNU/Linux bullseye/sid 5.9.0-4-rpi
linux /boot/vmlinuz-5.9.0-4-rpi
initrd /boot/initrd.img-5.9.0-4-rpi
fdtdir /usr/lib/linux-image-5.9.0-4-rpi/
append LABEL=ROOT net.ifnames=0 consoleblank=0 rw
label l0r
menu label Debian GNU/Linux bullseye/sid 5.9.0-4-rpi (rescue target)
linux /boot/vmlinuz-5.9.0-4-rpi
initrd /boot/initrd.img-5.9.0-4-rpi
fdtdir /usr/lib/linux-image-5.9.0-4-rpi/
append LABEL=ROOT net.ifnames=0 consoleblank=0 rw single
"disk-image.qcow2" has msdos partition table with a single ext4 partition.
I got the attached kernel panic (screenshot attached).
I put disk-image.qcow2 at
http://153.240.174.134:64193/disk-image.qcow2 (336 MB).
I am unsure if I should file a bug report to some Debian package
regarding on this...
Best regards, Ryutaroh
