@phrancesco - You may find some success by piecing together what you are able from this thread about PXE-booting UEFI
In your case (and with a healthy dose of willingness-to-experiment - even if it’s not your “ideal”), the major deviations would likely be:
- Ensure that the enlist-able machine(s) you want to commission are, in fact, set to boot legacy BIOS
- Modify the
dnsmasq.conf
entries to map to each enlist-able machine’s architecture (RFC4578) (see this comment for background/more info; you’re likely fine witharch,7
andarch,9
) - Modify the
dnsmasq.conf
entry fordhcp-boot
to belpxelinux.0
(the “legacy” version of PXE boot loader - i.e. non-UEFI version)
That said, if your enlist-able machine(s) are capable of supporting UEFI, definitely give that a go since things are made much smoother (and faster) by doing so - especially if you modify the UEFI-BIOS setting for boot order to be PXE HTTP. That said, you mentioned them being “old” machines, so I outlined the above with their likely lack of UEFI support in mind.
As for logging (namely to watch MAAS attempt to PXE-boot your enlist-able machines), simply log in to your MAAS host (via SSH) and then follow along:
- If you installed via snap:
sudo tail -f /var/snap/maas/common/log/rackd.log | grep "provisioningserver\|sstreams"
- If you installed via apt:
sudo tail -f /var/log/maas/rackd.log