PXE not working after upgrading to 2.5.0

Users
,
21

It’s possible the issue did occur on 2.5 also, but I haven’t been able to verify as 2.5 seems to be unavailable. I was suggesting 2.5 as to me it was the last known good version to my environment.

22

I’m collecting logs and detail here.

23

my lab is on vmware fusion, I’ve the same issue on 2.6.0

27
271280×800 302 KB

25

hi, did you resolve that?

26

No. Reverting back to 2.4.2 allows me to PXE boot those servers, but at a loss of all the 2.5.x+ functionality.

27

I’ve reported that on bugs.launchpad.net here is the link is the link. Let’s see if someone has our same issue.

28

I’ve made the same thing… reverting back to 2.4.2 with the 2.5 and 2.6 the PXE boot on vmware fusion not works.

29

I’m facing the same problem. Is there really no solution other than downgrading to 2.4?

What can one do to help with moving the ball forward?

30

Having this same issue with a BL460c Gen8 on MAAS 2.5/2.6 (Legacy BIOS), this is blocking deployment.

31

For those still having this issue, this was my workaround:

if option arch = 00:00 {
    filename "pxelinux.0";
}

Insert this as a DHCP snippet at the subnet level and PXE will work.

32

Looking at this post, it seems like it may be a firmware issue with the NIC.

33

Hi,

i’m facing the same problem with maas 2.6 and maas 2.8.2 with the old bl460G6.

Does anyone has a solution ?

The dhcp snippet doesn’t work for me.

BR

34