** Changed in: seabios (Ubuntu)
Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned)
--
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
** Changed in: seabios (Ubuntu)
Importance: Medium => Low
--
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
This is the VNC screenshot of a failing boot with seabios 1.10 - it
eventually booted the commission kernel via iPXE. If using 1.13, the
screen is quite similar, but it gets stuck on "Booting from SAN device
0x81".
** Attachment added: "seabios_1.10_maas_ipxe_failure.png"
After building Focal OVMF with (verbose) debug enabled, got this log.
** Attachment added: "ovmf-boot-dbg.gz"
https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1873662/+attachment/5356742/+files/ovmf-boot-dbg.gz
--
You received this bug notification because you are a member of Ubuntu
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:
$
** Attachment added: "seabios-1.13-blank-failure.log"
https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1873662/+attachment/5356741/+files/seabios-1.13-blank-failure.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "seabios-1.10-failure.log"
https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1873662/+attachment/5356740/+files/seabios-1.10-failure.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
