iPXE discussion forum

Hi,

The version of iPXE embedded in the Xen HVM BIOS is not full featured so I would like to chainload a different version if the relevant feature indicators are not set in the DHCP request. I know how to do this with ISC DHCPD but I am stuck in an environment with dnsmasq. So far I can deal with the case where it is not iPXE with:

dhcp-match=IPXEBOOT,175
dhcp-option=175,8:1:1
dhcp-boot=net:#IPXEBOOT,undionly.kpxe
dhcp-boot=net:IPXEBOOT,http://<boot server>/boot.php

but I would like to dhcp-match to IPXEBOOT only when iscsi, menu, ... features are available.

Has anyone else managed to solve this?

Thanks,
James

(2013-05-10 08:41)James Dingwall Wrote: [ -> ]The version of iPXE embedded in the Xen HVM BIOS is not full featured so I would like to chainload a different version if the relevant feature indicators are not set in the DHCP request. I know how to do this with ISC DHCPD but I am stuck in an environment with dnsmasq. So far I can deal with the case where it is not iPXE with:

dhcp-match=IPXEBOOT,175
dhcp-option=175,8:1:1
dhcp-boot=net:#IPXEBOOT,undionly.kpxe
dhcp-boot=net:IPXEBOOT,http://<boot server>/boot.php

but I would like to dhcp-match to IPXEBOOT only when iscsi, menu, ... features are available.

Has anyone else managed to solve this?

One option would be to have your DHCP infrastructure set up to hand out only undionly.kpxe, and have an embedded script within undionly.kpxe which boots from http://<boot server>/boot.php.

Michael

I had the same issue using ESXi. Embedding the script is definitely an option unless you use a dynamic script. An alternative that worked for me was just to build ipxe.iso and use that as a virtual CD/DVD and boot from that.