XCP-ng: Unable to select Grub2 UEFI pxe loader

Support
, , ,
1

Hi All,

Problem:

  • I’ve added a XCP-ng Operating system to foreman. I have selected the OS family as “XenServer”.
  • I’ve configured a Grub2 template based upon xcp-ng’s documentation.
  • When I click “create host” and select the the OS the PXEGrub2 template is correctly resolved when clicking “Resolve” at “Provisioning Templates” under “Operating System”.
  • But I am unable to select “Grub2 UEFI” as the PXE loader. I am only able to select PXELinux BIOS.

Expected outcome:
Being able to select “Grub2 UEFI” as the PXE loader.

Foreman and Proxy versions:
Foreman: 3.8
Foreman Proxy: 3.8

Foreman and Proxy plugin versions:
foreman-tasks 8.3.3
foreman_fog_proxmox 0.14.2
foreman_puppet 6.2.0
foreman_remote_execution: 11.1.1
foreman_salt 15.2.2
foreman_setup 8.0.1

Distribution and version:
Almalinux 8.9

Kind regards,
Goestin

2

Did you get any resolution for this issue, @goestin ? I also created a new family and have same outcome.

3

Hi @elianevidal , nope i didn’t manage it. I finally resorted to using legacy bios.

However at this moment i’m tasked with a batch of new servers which no longer work using PXELinux so I am forced to use UEFI pxe. So one year later i’m back again at this problem.

Where I am now:

  • If I select “None” for PXE Loader, then no “supersede server.filename” is set in the in the resulting dhcpd.leases record. Thus we can provide some manual filename in the dhcpd configuration. (eg “grubx64.efi”).

  • However, on foreman 3.8 (I know its old) it’s “grubx64.efi” (via “grub2/shim.efi”) doesnt contain the required “multiboot2” and “module2” modules as specified by the xcp-ng 8.3 documentation:

    • menuentry “XCP-ng Install (serial)” {
      multiboot2 /EFI/xcp-ng/xen.gz dom0_mem=2048M,max:2048M watchdog
      dom0_max_vcpus=4 com1=115200,8n1 console=com1,vga
      module2 /EFI/xcp-ng/vmlinuz console=hvc0 console=tty0 install
      module2 /EFI/xcp-ng/install.img
      }

  • At this point i’m trying to find or build a grubx64.efi which does contain those modules AND looks for the grub2.cfg provisioned by foreman.

So, no solution yet, hopefully i’ve got something going this week.

Cheers!