Opened 13 years ago
Closed 8 years ago
#9120 closed defect (obsolete)
pxe boot over subnet fails
| Reported by: | Thomas Besser | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.0.10 |
| Keywords: | pxe extpack | Cc: | |
| Guest type: | Windows | Host type: | Linux |
Description (last modified by )
We used VirtualBox 4.0.4 (without extpack) without problems to boot with pxe (pcnet devices) over subnet boundaries.
After upgrading 4.0.10 and installation of the extension pack (because usb2 support), pxe boot over subnet fails for all devices (intel and pcnet!). The pxe client in virtualbox uses the IP of the dhcp relay agent by mistake instead of the IP of the gateway/router, so a "PXE-E32 open timeout" occurs (look at attached screenshot).
The "dhcp offer" (wireshark snippet, attached) seems to be correct for me. Also attached the mandatory vbox.log
Regards Thomas
Attachments (3)
Change History (11)
by , 13 years ago
| Attachment: | virtualbox-pxe-relay-as-gateway.jpg added |
|---|
comment:1 by , 13 years ago
Unfortunately no change with version 4.1 of virtualbox.
Problem still exists.
Regards Thomas
comment:2 by , 13 years ago
No change with 4.1.2 of virtualbox.
Problem still exists.
Regards Thomas
comment:3 by , 13 years ago
No change with version 4.1.4, 4.1.6 of virtualbox.
Problem still exists.
Regards Thomas
comment:4 by , 13 years ago
Some additional information:
had the same error in a pxe implementation in a physical nic from intel. Boot ROM was quite old (from 2001). After flashing it with the intel boot agent to the newest version, the bug went away.
This pxe of the nic now does work like it should and sets the gateway correct.
I'm use also qemu-kvm for virtualization, their pxe implementation (etherboot) works also like expected.
Please fix this annoying bug.
Regards Thomas
comment:5 by , 13 years ago
Installed virtualbox version 4.1.8 today and the appropriate extpack.
Error in pxe implementation still exists
:-(
comment:6 by , 13 years ago
If you do not have the Oracle extpack installed it means the PXE implementation you're using is a somewhat modified Etherboot 4.5.2 build. So all bugs which are in that Etherboot version will also show in VirtualBox.
Do you have any information what Etherboot version fixed this? We could update.
It's actually on our todo list to switch to gPXE/iPXE, but we have so many other things to do...
comment:7 by , 13 years ago
Hi Klaus,
thanks for the sign of life according to this ticket. I was just before to give up this issue.
I need the extpack because of USB 2.0 support. So do I understand you right, that with extpack the whole (not only for intel cards) pxe part is not etherboot? What else then?
I tested qemu/kvm with etherboot version 5.4.4 which does not have this bug.
Regards Thomas
comment:8 by , 8 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → obsolete |
| Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
Screenshot PXE client Virtualbox