ipxe initialising devices fog stuck

[Wayne Workman]

@emyle Try undionly.kkpxe for that architecture. Just change the filename in there and restart dhcpd.

[Emyle]

This post is deleted!

[Emyle]

Thanks for you’r reply.

I modified the dhcp.conf file
And restart the dhcp service with this command : sudo service isc-dhcp-server restart
Then I have retry, the same problem, it’s stucked on iPXE intialising devices…

[george1421]

@emyle What version of FOG are you using?

Is this just hyper-v VM hanging or are physical machines hanging too?

[Emyle]

Thanks for u reply.

I’m using the latest version of fog 1.5.

It is the same on physical machine…

[george1421]

@emyle Ok just for clarity, you have a physical machine that is hanging at initializing devices.

What hardware is this (manufacturer and model)? We typically see this with uefi based systems and not so much with bios based systems.

Based on the system UUID it doesn’t appear to be a dell system here.

[edit] I just looked up the mac address of this VM and its a hyper-v VM. So its a virtual machine that is not initializing devices. So is this a type 1 or type 2 hyper-v? What OS is the hyper-v running under? If you try to pxe boot a physical machine, does it get stuck at the same point?

[Emyle]

thanks for reply.

in my physical machine it’s not booting on pxe…

my laptop is dell latitude 3340

my network card :Intel dual band wireless-AC 7260

It’s generation 1 and it’s window 10 1803 running

[Wayne Workman]

@emyle Is this Dell physically connected to the network or are you trying to boot over wifi?

[Emyle]

Thanks for you’r reply.
my laptop use Wifi connection.
On hyper-v i have the same switch for fog and the test machine.

[Sebastian Roth]

@Emyle iPXE does have some WIFI drivers but I’d say it’d be pure luck if it’d support your wireless NIC out of the box. FOG does not to imaging over wireless as of now. We don’t add wireless drivers to the kernel. It’s very tricky to do PXE booting off a WIFI NIC and we can’t support that.

[Emyle]

Hello,

I come back to you because I always have same problems, this time I connected a cable ethernet and modify parameter of the network card on Hyper - v.

[george1421]

@emyle We see a number of people posting that Hyper-V 1803 causes iPXE to stop on “Initializing devices…” This is not directly related to FOG, but changes Microsoft has done in 1803 that causes iPXE to break. FOG uses another project “iPXE Project” as its network boot loader.

I can find references that 1709 is broken, but they report that 1803 is working: http://forum.ipxe.org/showthread.php?tid=10998 and https://forums.fogproject.org/topic/11348/hyper-v-and-pxe-boot-to-fog-problems

My recommendation would be to switch to another type-2 hypervisor (yes I know hyper-v is not a type-2 hypervisor) like VMWare Workstation or Virtual Box until Microsoft can fix their hypervisor.

[Peterkegarcia]

@Wayne-Workman Worked for me