This could well be a MAAS bug (or even iPXE), as I'm not really sure in which component the flaw is. But given that MAAS+OVMF works, and I've confirmed both seabios and OVMF are using the same ipxe ROM, I believe this is a seabios issue.
MAAS PXE message sent to deployed guests is like below: $ curl tftp://localhost/ipxe.cfg-52:54:00:ac:e9:7e #!ipxe # Boot the locally attached hard drives. On failure try the next locally # attached hard drive. Fail on the last hard drive, if booting fails. sanboot --no-describe --drive 0x80 || sanboot --no-describe --drive 0x81 || sanboot --no-describe --drive 0x82 || sanboot --no-describe --drive 0x83 This command was executed inside MAAS VM (the MAC address is for the nvme guest). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873662 Title: maas/pxe cannot boot with nvme device (ovmf works) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1873662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
