FOG & iPXE Configuring net0... slowly

[fradlo]

Hello,

We’ve just recently installed a FOG server. It seems to be working so far as we’ve tested, but after chainloading into iPXE it seems to hang at the “configuring net0(MAC address)” step. I feel like it shouldn’t be hanging for 4-5 minutes at this step before continuing on to the menu. I’ve tried different kernals, different hosts, different .pxe, .kpxe, and kkpxe. What am I missing? What is happening at this stage exactly? Driver for the NIC loading? I can't find anything really describing this issue.

I've opened up a thread on the FOG forums as well:
https://forums.fogproject.org/topic/1137...et0-slowly

[NiKiZe]

How do you boot ipxe? and which iPXE binary are you booting? (have you tried for example ipxe.usb from http://boot.ipxe.org ?)
Which NIC is in the machine? (PCIID of the device, if running linux use lspci -nn)

[fradlo]

FOG chainloads iPXE after the Intel Boot Agent PXE. This is what comes along with the 1.4.4 version of FOG

The iPXE version shows iPXE 1.0.0+ (64865)

NIC is a Intel 82579LM Gigabit Network Connection (8086:1502)

Also tried an HP with Intel Ethernet Connection I219-LM (8086:156f)

[NiKiZe]

64865 Is from April 2017 https://git.ipxe.org/ipxe.git/commitdiff/64865
Always try latest master as described above. The reason for testing these known builds is to also know that it is not any kind of build config that is causing issues.

We still don't know what you are booting in terms of undionly.kpxe or ipxe.pxe (assuming you are booting in legacy mode)
For intel nics you could also use intel.pxe, other variants is not recommended.

When we know a bit more you could then build iPXE with debug flags enabled...
For example if you are using ipxe.pxe then building with make bin/ipxe.pxe DEBUG=intel will give intel specific debug output which could give you information about what the nic does. Then switching to DEBUG=intel,dhcp would also show DHCP related debug messages.