iPXE discussion forum
problems building vbox rom - Printable Version

+- iPXE discussion forum (http://forum.ipxe.org)
+-- Forum: iPXE user forums (/forumdisplay.php?fid=1)
+--- Forum: General (/forumdisplay.php?fid=2)
+--- Thread: problems building vbox rom (/showthread.php?tid=8428)



problems building vbox rom - iucounu9 - 2017-03-02 20:33

Hi,

I'm trying to rebuild a VirtualBox PXE ROM to include ELF, bzImage and a few other protocols as I am getting an exec format error. So I uncommented these in config/general.h and then ran the build as follows:

make CONFIG=vbox bin/intel--virtio-net--pcnet32.isarom

It builds fine but the protocols do not show up in the banner when loading, just the previous ones. Of course I removed the old ROM I'd built with the default protocols, and installed the new one with the extra protocols enabled with vboxmanage (as described).

Is there something I am missing in the build process?

Thanks for any help,

Cam


RE: problems building vbox rom - NiKiZe - 2017-03-02 20:41

I'm assuming you have read the Readme about vbox, copy found at: https://git.ipxe.org/ipxe.git/blob/HEAD:/src/config/vbox/README
And especially the size constraint part.

Remember that when CONFIG=vbox is used, the config files from that directory is used so changes needs to be done in those files (described in more detail at http://ipxe.org/appnote/named_config )

I don't think much features will fit in the above mentioned size constraint, so the usual way to handle that in vbox is to have DHCP config or script that checks the features, and if some feature, such as menu is missing then a more full version of ipxe is loaded over the network first before bzImage can/is booted. One ISC DHCP config that checks the ipxe features option can be found at: https://gist.github.com/robinsmidsrod/4008017#file-ipxe-green-conf I know Robin uses vbox so that config is likely done for just this use-case.


RE: problems building vbox rom - iucounu9 - 2017-03-03 15:17

Hi,

Thanks for the reply. I added the relevant lines to general.h in the vbox dir, after it didn't work the first time, but I'll check that I did it the right way from that link you sent.

Regarding the size constraint, I did see that, but it confused me because when I compiled it the first time with the defaults, it was 62464b in size, and it definitely loaded (I could see ipxe in the banner, and TFTP started working), however, when I recompiled to get rid of the exec format error, the resultant binary was actually a few bytes smaller (which also mystified me).

It looks like I probably won't be able to use it, as it was supposed to be a simple fix for a net boot issue on the network, so I don't think I'll be able to get the time to add more images to the PXE setup.

Thanks very much for the help though.

Kind regards,

Campbell

(2017-03-02 20:41)NiKiZe Wrote:  I'm assuming you have read the Readme about vbox, copy found at: https://git.ipxe.org/ipxe.git/blob/HEAD:/src/config/vbox/README
And especially the size constraint part.

Remember that when CONFIG=vbox is used, the config files from that directory is used so changes needs to be done in those files (described in more detail at http://ipxe.org/appnote/named_config )

I don't think much features will fit in the above mentioned size constraint, so the usual way to handle that in vbox is to have DHCP config or script that checks the features, and if some feature, such as menu is missing then a more full version of ipxe is loaded over the network first before bzImage can/is booted. One ISC DHCP config that checks the ipxe features option can be found at: https://gist.github.com/robinsmidsrod/4008017#file-ipxe-green-conf I know Robin uses vbox so that config is likely done for just this use-case.