Here the results from 0.5 vs 0.6
It is not meant to boot through, just to find transfer and load something on
netboot.
I think the behavior try-net-boot vs giving-up is different and should
represent the reported issue.
# Good case:
>>Start PXE over IPv4.
Station IP address is 10.0.2.15
Server IP address is 10.0.2.2
NBP filename is kernel.efi
NBP filesize is 15014280 Bytes
Downloading NBP file...
NBP file downloaded successfully.
BdsDxe: loading Boot0001 "UEFI PXEv4 (MAC:525400123456)" from
PciRoot(0x0)/Pci(0x3,0x0)/MAC(525400123456,0x1)/IPv4(0.0.0.0,0x0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)
BdsDxe: starting Boot0001 "UEFI PXEv4 (MAC:525400123456)" from
PciRoot(0x0)/Pci(0x3,0x0)/MAC(525400123456,0x1)/IPv4(0.0.0.0,0x0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)
# Bad Case:
UEFI Interactive Shell v2.2
EDK II
UEFI v2.70 (Ubuntu distribution of EDK II, 0x00010000)
Mapping table
BLK0: Alias(s):
PciRoot(0x0)/Pci(0x1,0x1)/Ata(0x0)
Press ESC in 3 seconds to skip startup.nsh or any other key to continue.
It is not that in the bad case it would not see the device at all, when
it failed to net-boot you can go "exit" then "device menu" and then
network devices. And you can see the virtio-net like
Name iPXE Firmware product name
Version 1.21.1+git-20220113.fbbdc3
926-0ubuntu2
Driver virtio-net
Device 0000:00:03.0
MTU _
Default gateway _
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2133157
Title:
ovmf 2024.02-2ubuntu0.6 broke UEFI network boot for VMs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/2133157/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
