MAAS

  1. Bug #1879012
  2. Comment #0

Comment 0 for bug 1879012

Revision history for this message
Lee Trager (ltrager) wrote : Shim does not hand off networking during HTTP boot

When using MAAS to HTTP boot on x86_64 UEFI grub drops to the command line. net_ls_addr shows the system has no address. If I run net_dhcp I get an address. I can then download the remote grub.cfg file and continue boot.

When reproducing with QEMU you have to manually reconfigure the boot order to try HTTP before TFTP:

# efibootmgr -v
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0003,0001,0000,0004
Boot0000* UiApp FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)
Boot0001* UEFI QEMU QEMU HARDDISK PciRoot(0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/SCSI(1,1)N.....YM....R,Y.
Boot0002* UEFI PXEv4 (MAC:00163E03BE1A) PciRoot(0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00163e03be1a,1)/IPv4(0.0.0.00.0.0.0,0,0)N.....YM....R,Y.
Boot0003* UEFI HTTPv4 (MAC:00163E03BE1A) PciRoot(0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/MAC(00163e03be1a,1)/IPv4(0.0.0.00.0.0.0,0,0)/Uri()N.....YM....R,Y.
Boot0004* EFI Internal Shell FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
# efibootmgr -o 0003,0002,0001,0004
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0003,0002,0001,0004
Boot0000* UiApp
Boot0001* UEFI QEMU QEMU HARDDISK
Boot0002* UEFI PXEv4 (MAC:00163E03BE1A)
Boot0003* UEFI HTTPv4 (MAC:00163E03BE1A)
Boot0004* EFI Internal Shell

grub> net_ls_addr
grub>
grub> net_dhcp
efinet0:dhcp 00:16:3e:03:be:1a 10.0.0.75
grub> configfile (http,10.0.0.2:5248)/grub/grub.cfg-default-amd64
Booting under MAAS direction...

I believe the bug is in grub or the shim. As MAAS receives its bootloaders from the stream at images.maas.io generated by lp:maas-images this effects all versions of MAAS.