[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI

[Łukasz Zemczak]

Hello Lee, or anyone else affected,

Accepted ipxe into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ipxe/1.0.0+git-20180124.fbe8c52d-
0ubuntu2.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ipxe (Ubuntu Bionic)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shim in Ubuntu.
https://bugs.launchpad.net/bugs/1789319

Title:
  Unable to load shimx64.efi using iPXE over UEFI

Status in MAAS:
  Triaged
Status in grub2 package in Ubuntu:
  Invalid
Status in ipxe package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  Invalid
Status in ipxe source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  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";
  }

  [Test case]
  Minimal test case:

  Run the following command and ensure it boots (assuming a EFI system with shim and grub):
  sudo kvm -bios /usr/share/OVMF/OVMF_CODE.fd -device virtio-net,netdev=n1 -netdev user,id=n1,tftp=/boot/efi/EFI/ubuntu,bootfile=shimx64.efi

  Optimally, also do the MAAS thing.

  [Regression potential]
  I switched the ipxe-qemu packages to build in qemu mode, which makes things use OVMF's internal network stack (so things might work differently with some bootloaders or something when netbooting). 

  It might do other stuff, too, I don't really know. That said, the
  configuration is specifically for qemu, and used by other
  distributions, so this aligns us more closely with them, reducing
  chances of breaking stuff.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1789319/+subscriptions