Fixed in yakkety: grub2 (2.02~beta2-36ubuntu11) yakkety; urgency=medium
* debian/control: don't force building with GCC 5 when 6 is now the default. * support_module_without_symbol_table.patch: fix checks for modules without a symbol table to be allowed, since binutils' 'strip --stripunneeded' no longer leaves a symbols section around after stripping. * Fix support for IPv6 PXE booting under UEFI: - grub_add_grub_env_set_net_property.patch: add grub_env_set_net_property. - misc-fix-invalid-char-strtol.patch: fix strto*l methods invalid chars. - net_read_bracketed_ipv6_addr.patch: read bracketed IPv6 addresses. - bootp_new_net_bootp6_command.patch: add new bootp6 commands. - efinet_uefi_ipv6_pxe_support.patch: teach efinet to allow bootp6. - bootp_process_dhcpack_http_boot.patch: process DHCPACK, support HTTP. - efinet_set_network_from_uefi_devpath.patch: configure network from the devpath provided by the UEFI firmware. - efinet_set_dns_from_uefi_proto.patch: set DNS nameservers and search domains from the UEFI protocol. ** Changed in: grub2 (Ubuntu) Status: In Progress => Fix Released -- 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: Fix Released 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 _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp