Public bug reported:
While implementing the complete UEFI HTTP booting path for MAAS I have
hit a roadblock. Grub2 is loaded but then fails to request the
/grub/grub.cfg as it does when booting with UEFI PXE (aka. TFTP).
The dhcpd.conf has the following in it to tell the UEFI firmware to load
the bootx64.efi (signed-shim) over HTTP.
} elsif option arch = 00:0f {
# uefi_amd64_http
filename "http://192.168.122.2:5248/bootx64.efi";;
option vendor-class-identifier "HTTPClient";
} elsif option arch = 00:10 {
# uefi_amd64_http
filename "http://192.168.122.2:5248/bootx64.efi";;
option vendor-class-identifier "HTTPClient";
} elsif option arch = 00:0B {
This works correctly because the UEFI firmware does load the bootx64.efi
then the shim loads the grubx64.efi over HTTP.
2019-03-27 23:21:59 provisioningserver.rackdservices.http: [info] bootx64.efi
requested by 192.168.122.193
2019-03-27 23:21:59 provisioningserver.rackdservices.http: [info] grubx64.efi
requested by 192.168.122.193
No other requests are received from that point forward. Grub2 reports
the following error:
Error: Unexpected network error.
Checking the grub2 environment it does seem wierd that none of the
networking variables are set they are completely blank.
grub_cpu=x86_64
grub_platform=efi
net_default_ip=(null)
net_default_mac=(null)
net_default_server=
package_version=2.02+dfsg1-12ubuntu2
prefix=
pxe_default_server=
root=
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822007
Title:
Grub fails to request the /grub/grub.cfg over HTTP when booting with
UEFI HTTP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1822007/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
