iPXE doesn't boot

Discussions about using non Windows and Linux guests such as FreeBSD, DOS, OS/2, OpenBSD, etc.
Post Reply
Ajax
Posts: 3
Joined: 23. Jun 2014, 17:27

iPXE doesn't boot

Post by Ajax »

Running virtualbox-ose-4.3.12_1 on FreeBSD 10-REL with DHCP, NFS and TFTP properly setup (physical hardware machines boots from configuration). However virtual machines doesn't boot, stucking at bootloader. Plus "ignoring unsupported root path" message looks suspicious. Anyone could help solving this problem?
Screen Shot 2014-06-23 at 18.33.17.png
Screen Shot 2014-06-23 at 18.33.17.png (42.35 KiB) Viewed 6170 times
Ajax
Posts: 3
Joined: 23. Jun 2014, 17:27

Re: iPXE doesn't boot [UPD]

Post by Ajax »

UPDATE
After grabbing Intel PXE ROM from rom-o-matic and loading it with

Code: Select all

VBoxManage setextradata global VBoxInternal/Devices/pcbios/0/Config/LanBootRom /root/work/PXE-Intel.rom
finally made guests loadable yet it still seems to be a bug either in iPXE used by VirtualBox or in iPXE itself.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: iPXE doesn't boot

Post by Perryg »

Did you install the Extension Pack?
Ajax
Posts: 3
Joined: 23. Jun 2014, 17:27

Re: iPXE doesn't boot

Post by Ajax »

No, since was trying to stay within OSE. Yet testing with Intel ROM from Extensions Pack let it boot properly, as well as generated one on above mentioned website. Looks like a iPXE problem.
klaus
Oracle Corporation
Posts: 1110
Joined: 10. May 2007, 14:57

Re: iPXE doesn't boot

Post by klaus »

Note that it's confusing if you say "Intel PXE" and are talking about "gPXE configured to support E1000". Intel has their own PXE ROM (which we are including in the extension pack, Intel doesn't allow distributing the sources, only the binaries)...

It's possible that your PXE setup somehow doesn't like iPXE. But before you blame iPXE, please try a recent version of iPXE. At the moment the iPXE sources used to produce the ROM included in the VirtualBox base package aren't anywhere near latest and greatest, which means it might be lacking bug fixes.
Post Reply