Comment 3 for bug 1805920

Hi Vern,

Based on your description it would sound like this is *not* a MAAS issue, but rather, it could either be a networking issue, a misconfiguration issue or a ipxe issue.

To start, from the ipxe side:

1. MAAS doesn't support PXE booting over VLANs.
2. MAAS doesn't support ipxe. We rely on the VMs on booting pxelinux emulation but MAAS doesn't pass a ipxe rom, nor configures ipxe at all.

Second, how is your network configuration? While I understand you have 3 machines running MAAS, and only VMs that have DHCP running locally can PXE boot, I'm wondering:

1. Can you confirm that all bridges of the pods on the underlying network are using a /physical/ bridge in the /same/ vlan ?
2. What's the machines interface configuration? How about the bridge configuration?
3. To what interfaces are the MAAS DHCP servers responding to? (e.g. ps faux | grep dhcpd)
4. Can you confirm that VMs inside pod on infra1 can communicate with VMs inside pod of infra2 or 3?

Lastly, I have a feeling that this is likely related to the network configuration itself, or the configuration of the bridges:
 1. For networking, is STP/Portfast enabled? https://docs.maas.io/2.5/en/installconfig-network-stp
 2. Does the bridge where the VMs use, configured with STP and/or a long forward-delay? https://wiki.libvirt.org/page/PXE_boot_(or_dhcp)_on_guest_failed