This is a regression from Bookworm, I think. In this version, even if
available, qemu never tries to run efi-virtio.rom. Instead it just goes
to the EDK2 internal EFI shell (depending on other config, sometimes also the
internal PXE/HTTPBoot support).
I tried setting the romfile for virtio-net-pci, no change.
BIOS works:
| $ qemu-system-x86_64 -machine q35 -nic user,model=virtio -boot n -nographic
| SeaBIOS (version 1.16.3-debian-1.16.3-2)
|
|
| iPXE (https://ipxe.org) 00:02.0 CA00 PCI2.10 PnP PMM+06FC6CF0+06F06CF0 CA00
|
|
|
| Booting from ROM...
| iPXE (PCI 00:02.0) starting execution...ok
| iPXE initialising devices...
|
|
|
| iPXE 1.21.1+git20250317.42a29d56+dfsg-1 -- Open Source Network Boot Firmware --
| https://ipxe.org
| Features: VLAN DNS HTTP HTTPS iSCSI NFS TFTP AoE ELF MBOOT PXE bzImage Menu PXEX
| T
|
| Press Ctrl-B for the iPXE command line...
EFI does not:
| $ qemu-system-x86_64 -machine q35 -nic user,model=virtio -boot n -nographic -bios /usr/share/qemu/OVMF.fd
| BdsDxe: starting Boot0001 "EFI Internal Shell" from Fv(7CB8BDC9-F8EB-4F34-AAEA-3EE4AF6516A1)/FvFile(7C04A583-9E3E-4F1C-AD65-E05268D0B4)
Am I doing something stupid here? ipxe-qemu is from unstable with the
ROM changes already.
Bastian