group.of.nepali.translators team mailing list archive

[LaMont Jones <lamont.jones@xxxxxxxxxxxxx>]

** Attachment added: "screenshot of the failed attempt"
   https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1229458/+attachment/4724000/+files/1229458-screenshot.jpg

** Changed in: grub2 (Ubuntu)
       Status: Fix Released => In Progress

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1229458

Title:
  grubnetx64.efi tftp client does not work over ipv6

Status in MAAS:
  Confirmed
Status in grub2 package in Ubuntu:
  In Progress
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Committed
Status in grub2-signed source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Trying to PXE boot (with UEFI) over IPv6 with grub. This is especially relevant for MAAS users in IPv6 setups.

  [Test cases]
  0) Setup PXE boot infrastructure (https://wiki.ubuntu.com/UEFI/SecureBoot-PXE-IPv6, also https://github.com/openSUSE/kiwi/wiki/Setup-PXE-boot-with-EFI-Using-GRUB2 contains relevant information)
  1) Attempt to PXE boot (with UEFI) over IPv6 a system.

  Testers can use grubnetx64.efi.signed from
  http://archive.ubuntu.com/ubuntu/dists/xenial-
  proposed/main/uefi/grub2-amd64/current/ once the package is available
  in proposed.

  
  [Regression potential]
  Possible regressions include any issues in routing IPv4 or IPv6 and/or retrieving files over PXE/tftp via grub. Ping is a good way to validate that routing is being done correctly, so is actually booting using the build grubnetx64.efi.

  ---

  Testing using the pre-built grubnetx64.efi, I am not able to use the
  tftp client support within grub2 to load configs (/kernels/initrds)
  over the network.  This works fine if using IPv4.

  grubnetx64.efi is being loaded over the network (via shim no less), so
  the firmware's network stack is definitely up and working.  But when
  grub tries to load grub.cfg via the default path, it fails with:

    error: couldn't send network packet.

  This message is repeated, approximately once every three seconds.  It
  looks to be an infinite loop; at least, the message is repeated more
  than 100 times.  But sometimes, when I've not been paying close
  attention to the boot, I get a grub shell instead.  In that case, the
  grub shell shows:

  grub> echo $root
  tftp,0.5.0.24
  grub> set
  [...]
  net_default_server=
  net_efinet2_boot_file=8:23f::2]/bootx64.efi
  net_efinet2_ip=0.0.0.0
  net_efinet2_mac=02:3f:00:00:00:00
  [...]
  prefix=(tftp,0.5.0.24)/grub
  pxe_default_server=
  root=tftp,0.5.0.24
  [...]
  grub>

  The actual server IP is 2001:1938:23f::2.

  I've booted a locally-generated (self-signed) grubnetx64.efi with
  grub-bootstrap.cfg modified to call 'set' first, and I get identical
  output for all of the network-related variables.

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