[Bug 2044549] Re: pxe boot on arm64 stopped working

[Dmytro Kazantsev]

Hi MAAS team, I wanted to reopen this issue since I faced exactly the
same problem. I'm testing GIGABYTE servers R282-P92-00. There are 6
servers which can not boot Ubuntu Jammy 22.04 via PXE boot under MAAS
control. When PXE boot happens I see that IP address gets assigned and
server receives two files bootaa64.efi and grubaa64.efi via TFTP. But
after that the boot process stops and the console shows that the server
drops to the GRUB shell. Just wanted to let you know that after BIOS
upgrade from 31r to 33j very first time the server was able to
successfully perform PXE boot, but then after next restart and attempt
to boot from the network the same problem is visible again and
reproducible every time I try to boot from the network. So there is
definitely something wrong in the HW or in GRUB because it was able to
successfully perform PXE boot immediately after the BIOS upgrade and
then again failed.

** Attachment added: "GRUB.png"
   https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2044549/+attachment/5817827/+files/GRUB.png

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

Title:
  pxe boot on arm64 stopped working

Status in grub2 package in Ubuntu:
  Invalid

Bug description:
  We have a lab with eight arm64 machines which are deployed from MAAS (also on arm64). 
  Two weeks ago we noticed the commissioning in MAAS is not working.
  We can see MAAS sends two files (bootaa64.efi and grubaa64.efi) as requested and then machine goes to grub prompt.
  @alexsander-souza from MAAS team had a look and he suspects grub issue. net_bootp command returns "error: couldn't send  network packet".
  Sometimes when machine is power cycled it can deploy again, but not always.
  Any idea how to debug this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2044549/+subscriptions