Post Reply 
 
Thread Rating:
  • 2 Vote(s) - 4.5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
VirtualBox compatibility ?
2016-08-03, 08:50
Post: #3
RE: VirtualBox compatibility ?
The error message you're getting indicates that you're not getting any response from your DHCP server, so your network is most likely screwed up in some way. Are you using bridged or NAT networking? You should be using bridged networking if you want to get a response from the DHCP server on your local (host) network.

I had my own issue with 5.1.2, it couldn't even start VMs because of some funky DLL issue on Windows. I ended up rolling back to 5.0.26 and everything worked again.

Be aware that a custom iPXE ROM must never be more than 56KB (56 x 1024 bytes) large, or VirtualBox will silently fail to load it. This has bitten me a lot of times.

This is the shell function I use to build my vbox-compatible iPXE ROM:

Code:
make_vbox() {
    pushd "$HOME/src/forked/ipxe/src" >/dev/null &&
    make CONFIG=vbox bin/intel--virtio-net--pcnet32.isarom &&
    echo "Max size of VirtualBox ROM is 56KB, 57344 bytes" &&
    ls -l bin/intel--virtio-net--pcnet32.isarom &&
    prefix=$(date +%Y%m%d-%H%M%S) &&
    mkdir -p /ipxe/$prefix &&
    cp -v bin/intel--virtio-net--pcnet32.isarom /ipxe/$prefix/ &&
    echo -e "@echo off\r\nvboxmanage setextradata global VBoxInternal/Devices/pcbios/0/Config/LanBootRom C:\\Programs\\iPXE\\$prefix\\intel--virtio-net--pcnet32.isarom\r\nvboxmanage getextradata global enumerate\r\n" >/ipxe/setvboxrom.bat &&
    popd >/dev/null
}
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
VirtualBox compatibility ? - xhark - 2016-08-02, 22:32
RE: VirtualBox compatibility ? - robinsmidsrod - 2016-08-03 08:50



User(s) browsing this thread: 1 Guest(s)