Ticket #15846 (closed defect: fixed)
Booting iPXE using Intel vNIC fails - regression since 5.0.26 => Fixed in SVN
|Reported by:||robinsmidsrod||Owned by:|
|Version:||VirtualBox 5.1.4||Keywords:||ipxe intel|
I recently tried to upgrade from VirtualBox 5.0.26 to 5.1.4, and I had to rollback to 5.0.26 again, because I couldn't boot over the network using either my custom-built 56KB iPXE ROM or a stock version of ipxe.dsk (floppy image) booted via floppy emulation. In both cases when I start iPXE shell and run ifstat all of the packets counters show 0. If I run "dhcp" and run ifstat again it fails with error http://ipxe.org/err/040ee1, which indicates that no DHCP response or IPv6 SLAAC response reached the VM. What's actually interesting is that my DHCP server sees the DHCP DISCOVER and returns the DHCP OFFER, but the VM never sees this DHCP OFFER. I tried to enable --nictrace on the VM, which confirmed that the DHCP OFFER was present at that point, but iPXE never received it. Rebuilding ipxe with DEBUG=intel:3 didn't give any obvious pointers to what was wrong.
If I booted with virtio-net instead, everything worked as expected. My assumption is that the iPXE intel driver is no longer capable to speak with the new emulated intel vnic in 5.1.4. Just to confirm that there are no network issues here I booted up a Ubuntu VM and it had no issues communicating with the network and get a DHCP lease. I also tried all three intel vnics, and they behaved slightly different, but all broken in some way which prevented network packets from reaching iPXE. So my assumption is that the problem might be somewhere in the receive (RX) path.
Attached are log files for both 5.0.26 and 5.1.4. Hopefully you'll be able to figure out what the problem is.
- Summary changed from Booting iPXE using Intel vNIC fails - regression since 5.0.26 to Booting iPXE using Intel vNIC fails - regression since 5.0.26 => Fixed in SVN