virbtualbox efi mode dose not work

[IAseven]

Describe the bug

used iso file

exception

[antonym]

Try a different virtual network adapter?

ipxe/ipxe#977 (comment)

[neitsab]

I had started writing a bug report, but since the previous one has been turned into a Discussion here's a properly defined test case to make it reproducible:

VirtualBox/EFI: Booting on the combined ISO works only with the non-Intel network interfaces

• This bug persists when memory is increased beyond 8GB.

Describe the bug

Booting on the combined ISO works only with the non-Intel network interfaces, i.e. virtio-net, PCnet-PCI II (Am79C970A) and PCnet-FAST III (Am79C973) . Tested with;

• VirtualBox 7.1.4
• Arch Linux x86_64 host
• VM configured in EFI mode
• PIIX3 and ICH9 chipset

To Reproduce
Steps to reproduce the behavior:

1. Install VirtualBox 7.1.4 64-bits on Linux
2. Create a new VM using
   • the x86_64 Combined Legacy and UEFI iPXE Bootloaders ISO image
   • 8 GB of RAM
   • 4 cores
   • Enable EFI
   • 20 GB disk
3. Boot the VM: it gets stuck after file:/autoexec.ipxe... ok
4. Open the VM Settings, check that Chipset is PIIX3, Network Adapter 1 is using NAT and Intel PRO/1000 MT Desktop (82540EM) interface type
5. Change interface to virtio-net and renew the MAC address
6. Boot the VM: this time it works
7. Shut it down, repeat for all network interface types; none of the Intel ones work, only virtio and PCnet ones
8. Also change the Chipset (under System Settings) from PIIX3 to ICH9, to no avail.

Note: switching the interface to Bridge mode makes virtio-net not work anymore.

Expected behavior

VM boot on the combined ISO with default settings in EFI mode.

Screenshots

Stuck with the default network interface Intel PRO/1000 MT Desktop (82540EM):

Working when changed the interface to virtio-net / PCnet :

I'll try to ping upstream...