[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI
Lee Trager
lee.trager at canonical.com
Tue Aug 28 01:24:52 UTC 2018
** Description changed:
libvirt supports running in UEFI mode and uses iPXE to enable network
booting. When MAAS gives shimx64.efi, as it does on all UEFI systems, to
iPXE it chainloads grub but fails to the grub prompt. If I modify MAAS
to give grubx64.efi instead of shimx64.efi UEFI booting works.
+
+ Ideally iPXE would be modified to properly chainload the shim however
+ MAAS could also check the user-agent when returning the boot file as
+ followes.
+
+ if option arch = 00:00 {
+ # pxe
+ filename "lpxelinux.0";
+ } elsif option arch = 00:07 and exists user-class and option user-class = "iPXE" {
+ # iPXE uefi_amd64
+ filename "grubx64.efi";
+ } elsif option arch = 00:07 {
+ # uefi_amd64
+ filename "bootx64.efi";
+ } elsif option arch = 00:09 and exists user-class and option user-class = "iPXE" {
+ # iPXE uefi_amd64
+ filename "grubx64.efi";
+ } elsif option arch = 00:09 {
+ # uefi_amd64
+ filename "grubx64.efi";
+ } elsif option arch = 00:0B {
+ # uefi_arm64
+ filename "grubaa64.efi";
+ } elsif option arch = 00:0C {
+ # open-firmware_ppc64el
+ filename "bootppc64.bin";
+ } elsif option arch = 00:0E {
+ # powernv
+ filename "pxelinux.0";
+ option path-prefix "ppc64el/";
+ } elsif option arch = 00:1F {
+ # s390x
+ filename "boots390x.bin";
+ option path-prefix "s390x/";
+ } else {
+ # pxe
+ filename "lpxelinux.0";
+ }
** Description changed:
libvirt supports running in UEFI mode and uses iPXE to enable network
booting. When MAAS gives shimx64.efi, as it does on all UEFI systems, to
iPXE it chainloads grub but fails to the grub prompt. If I modify MAAS
to give grubx64.efi instead of shimx64.efi UEFI booting works.
Ideally iPXE would be modified to properly chainload the shim however
MAAS could also check the user-agent when returning the boot file as
- followes.
+ follows.
if option arch = 00:00 {
- # pxe
- filename "lpxelinux.0";
+ # pxe
+ filename "lpxelinux.0";
} elsif option arch = 00:07 and exists user-class and option user-class = "iPXE" {
- # iPXE uefi_amd64
- filename "grubx64.efi";
+ # iPXE uefi_amd64
+ filename "grubx64.efi";
} elsif option arch = 00:07 {
- # uefi_amd64
- filename "bootx64.efi";
+ # uefi_amd64
+ filename "bootx64.efi";
} elsif option arch = 00:09 and exists user-class and option user-class = "iPXE" {
- # iPXE uefi_amd64
- filename "grubx64.efi";
+ # iPXE uefi_amd64
+ filename "grubx64.efi";
} elsif option arch = 00:09 {
- # uefi_amd64
- filename "grubx64.efi";
+ # uefi_amd64
+ filename "grubx64.efi";
} elsif option arch = 00:0B {
- # uefi_arm64
- filename "grubaa64.efi";
+ # uefi_arm64
+ filename "grubaa64.efi";
} elsif option arch = 00:0C {
- # open-firmware_ppc64el
- filename "bootppc64.bin";
+ # open-firmware_ppc64el
+ filename "bootppc64.bin";
} elsif option arch = 00:0E {
- # powernv
- filename "pxelinux.0";
- option path-prefix "ppc64el/";
+ # powernv
+ filename "pxelinux.0";
+ option path-prefix "ppc64el/";
} elsif option arch = 00:1F {
- # s390x
- filename "boots390x.bin";
- option path-prefix "s390x/";
+ # s390x
+ filename "boots390x.bin";
+ option path-prefix "s390x/";
} else {
- # pxe
- filename "lpxelinux.0";
+ # pxe
+ filename "lpxelinux.0";
}
** Description changed:
libvirt supports running in UEFI mode and uses iPXE to enable network
booting. When MAAS gives shimx64.efi, as it does on all UEFI systems, to
iPXE it chainloads grub but fails to the grub prompt. If I modify MAAS
to give grubx64.efi instead of shimx64.efi UEFI booting works.
Ideally iPXE would be modified to properly chainload the shim however
MAAS could also check the user-agent when returning the boot file as
follows.
if option arch = 00:00 {
# pxe
filename "lpxelinux.0";
} elsif option arch = 00:07 and exists user-class and option user-class = "iPXE" {
# iPXE uefi_amd64
filename "grubx64.efi";
} elsif option arch = 00:07 {
# uefi_amd64
filename "bootx64.efi";
} elsif option arch = 00:09 and exists user-class and option user-class = "iPXE" {
# iPXE uefi_amd64
filename "grubx64.efi";
} elsif option arch = 00:09 {
# uefi_amd64
- filename "grubx64.efi";
+ filename "bootx64.efi";
} elsif option arch = 00:0B {
# uefi_arm64
filename "grubaa64.efi";
} elsif option arch = 00:0C {
# open-firmware_ppc64el
filename "bootppc64.bin";
} elsif option arch = 00:0E {
# powernv
filename "pxelinux.0";
option path-prefix "ppc64el/";
} elsif option arch = 00:1F {
# s390x
filename "boots390x.bin";
option path-prefix "s390x/";
} else {
# pxe
filename "lpxelinux.0";
}
** Description changed:
- libvirt supports running in UEFI mode and uses iPXE to enable network
- booting. When MAAS gives shimx64.efi, as it does on all UEFI systems, to
- iPXE it chainloads grub but fails to the grub prompt. If I modify MAAS
- to give grubx64.efi instead of shimx64.efi UEFI booting works.
+ libvirt supports creating virtual machines running in UEFI mode and uses
+ iPXE to enable network booting. When MAAS gives shimx64.efi, as it does
+ on all UEFI systems, to iPXE it chainloads grub but fails to the grub
+ prompt. If I modify MAAS to give grubx64.efi instead of shimx64.efi UEFI
+ booting works.
Ideally iPXE would be modified to properly chainload the shim however
MAAS could also check the user-agent when returning the boot file as
follows.
if option arch = 00:00 {
# pxe
filename "lpxelinux.0";
} elsif option arch = 00:07 and exists user-class and option user-class = "iPXE" {
# iPXE uefi_amd64
filename "grubx64.efi";
} elsif option arch = 00:07 {
# uefi_amd64
filename "bootx64.efi";
} elsif option arch = 00:09 and exists user-class and option user-class = "iPXE" {
# iPXE uefi_amd64
filename "grubx64.efi";
} elsif option arch = 00:09 {
# uefi_amd64
filename "bootx64.efi";
} elsif option arch = 00:0B {
# uefi_arm64
filename "grubaa64.efi";
} elsif option arch = 00:0C {
# open-firmware_ppc64el
filename "bootppc64.bin";
} elsif option arch = 00:0E {
# powernv
filename "pxelinux.0";
option path-prefix "ppc64el/";
} elsif option arch = 00:1F {
# s390x
filename "boots390x.bin";
option path-prefix "s390x/";
} else {
# pxe
filename "lpxelinux.0";
}
** Also affects: shim-signed (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shim-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1789319
Title:
Unable to load shimx64.efi using iPXE over UEFI
Status in MAAS:
Triaged
Status in ipxe package in Ubuntu:
New
Status in shim-signed package in Ubuntu:
New
Bug description:
libvirt supports creating virtual machines running in UEFI mode and
uses iPXE to enable network booting. When MAAS gives shimx64.efi, as
it does on all UEFI systems, to iPXE it chainloads grub but fails to
the grub prompt. If I modify MAAS to give grubx64.efi instead of
shimx64.efi UEFI booting works.
Ideally iPXE would be modified to properly chainload the shim however
MAAS could also check the user-agent when returning the boot file as
follows.
if option arch = 00:00 {
# pxe
filename "lpxelinux.0";
} elsif option arch = 00:07 and exists user-class and option user-class = "iPXE" {
# iPXE uefi_amd64
filename "grubx64.efi";
} elsif option arch = 00:07 {
# uefi_amd64
filename "bootx64.efi";
} elsif option arch = 00:09 and exists user-class and option user-class = "iPXE" {
# iPXE uefi_amd64
filename "grubx64.efi";
} elsif option arch = 00:09 {
# uefi_amd64
filename "bootx64.efi";
} elsif option arch = 00:0B {
# uefi_arm64
filename "grubaa64.efi";
} elsif option arch = 00:0C {
# open-firmware_ppc64el
filename "bootppc64.bin";
} elsif option arch = 00:0E {
# powernv
filename "pxelinux.0";
option path-prefix "ppc64el/";
} elsif option arch = 00:1F {
# s390x
filename "boots390x.bin";
option path-prefix "s390x/";
} else {
# pxe
filename "lpxelinux.0";
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1789319/+subscriptions
More information about the foundations-bugs
mailing list