You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mellanox FlexBoot is a modified iPXE, so we expected it would identify itself via this option as well. This doesn't appear to be case. An alternative method needs to be identified to conditionally set the filename option to the iPXE cfg file for FlexBoot.
Just a idea: FlexBoot requests dhcp-client-identifier with a fixed prefix (as far as I remember it has two or three prefixes dependent on the card model following by the card GUID. I don't know much about DHCP config, but maybe it is possible to use this prefix to tell we are dealing with FlexBoot?
I have a similar issue, with virtualbox (without the extension pack) pxe booting with a stripped down ipxe version which trigger the matching iPXE tag, but without the bzImage loading capacity...
We're using the DHCP user-class option 76 from a DHCP request to identify clients as iPXE ( (https://github.com/warewulf/warewulf3/blob/master/provision/etc/dhcpd-template.conf#L14).
Mellanox FlexBoot is a modified iPXE, so we expected it would identify itself via this option as well. This doesn't appear to be case. An alternative method needs to be identified to conditionally set the filename option to the iPXE cfg file for FlexBoot.
Discussion and debugging in #100.
The text was updated successfully, but these errors were encountered: