Win 10 Hyper-v VM unable to PXE boot

[Jaan]

Hi all…

I’ve been here before but can’t remember what i did to fix it…

Short story is i’ve had to rebuild the Fog server today.

Fog installed everything fine, Set a image definition in fog, fired up my Windows 10 VM (Image client). in hope to upload it to fog… and it just hangs @ initialising device.

I’m sure it’s something really really simple.

Anybody kick me in the right direction?

Legacy nic, non uefi. all the clients on site can boot to pxe fine, and upload a image. Just not my Hyper-v VM. I’m sure it’s something to do with hyper-v as all my physical machines are fine.

-Windows enviro-
Win10 1809 ltsc (vm running on hyper-v)
Server 2019 “1809”

-Fog Enviro-
Running Ubuntu 20.04.3 LTS
Fog 1.5.9

Thanks all

[Sebastian Roth]

@Jaan Searching the forums you can find many posts on this (1, 2, 3). Though all of them talk about older versions of Windows that caused the problem.

Now to tackle this I suggest you download the latest iPXE binaries from github, put those into /tftpboot on your FOG server and try again.

If that doesn’t help you might look into changing the FOG generated dhcpd.conf to use undionly.kpxe instead of the default undionly.kkpxe iPXE binary.

[Jaan]

@sebastian-roth said in Win 10 Hyper-v VM unable to PXE boot:

dhcpd.conf

Thanks for this Sebastian. I appreciate your response. I did see the other threads, but discounted them as the are different revision of HYPER-V, from what i understand my version is the troublesome one. I did have this working on the previous ltsc of ubuntu.

Thanks for the link to GITHUB also, i have downloaded them all and used the mv command in terminal to put them into /tftpboot.

Unfortunately this hasn’t resolved the issue. i have performed a reboot also.

I thought i was already using “undionly.kpxe” not kkpxe. As you can probably tell i’m a little green with this. I already have the below listed in my DHCP server… not sure where to find the dhcpd.conf file to edit it. Can i do this in the FOG GUI?

Thanks again

[Sebastian Roth]

@jaan said in Win 10 Hyper-v VM unable to PXE boot:

I did see the other threads, but discounted them as the are different revision of HYPER-V, from what i understand my version is the troublesome one. I did have this working on the previous ltsc of ubuntu.

I don’t use Hyper-V and therefore can’t give you any information on which version should work.

Unfortunately this hasn’t resolved the issue. i have performed a reboot also.

No reboot needed. The iPXE binaries are used as soon as they are in place. I was just going to say that you can check the iPXE version number on screen when it boots up to make sure it actually uses the newer binaries. But looking at the picture you posted initially I remember the version header is printer after the device initialization sequence. Too bad.

I already have the below listed in my DHCP server… not sure where to find the dhcpd.conf file to edit it. Can i do this in the FOG GUI?

Thanks again

Yes, obviously you use a Windows DHCP server and it’s set to use undionly.kpxe already. Don’t worry about the mentioned dhcpd.conf then. This is only used when FOG is configured to be the DHCP server in your network.