Project

General

Profile

Actions

Feature #16652

closed

UEFI Grub2 support for non-intel architectures

Added by Lukas Zapletal over 7 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
Orchestration
Target version:
Difficulty:
easy
Triaged:
Fixed in Releases:
Found in Releases:

Description

Foreman currently sets DHCP filename option to either grubx64.efi or grubia32.efi according the architecture of the host. We need to expand the list with more architectures so users can boot other platforms via Grub2 UEFI.

In order to achieve that, one only needs to generate Grub2 binary for particular architecture. Instead using traditional modular build:

grub2-mknetdir --net-directory=/root/grub

Foreman assumes the firmware is built into single file. If file is available in the OS, it can be simple copied. For example in Red Hats on several platforms grub2-efi package provides the EFI loader (e.g. /boot/efi/EFI/redhat/grubaa64.efi).

In other cases, it must be build from scratch (replace architecture with correct one):

grub2-mkimage -O powerpc-ieee1275 -d /usr/lib/grub/powerpc-ieee1275 -o /root/grubppc64.efi -p "" all_video boot btrfs cat configfile echo ext2 fat font gfxmenu gfxterm gzio halt hfsplus iso9660 jpeg loadenv loopback lvm mdraid09 mdraid1x minicmd normal part_apple part_msdos part_gpt password_pbkdf2 png reboot search search_fs_uuid search_fs_file search_label serial sleep syslinuxcfg test tftp video xfs linux

Then copy the file to TFTP Smart Proxy under /var/lib/tftproot/boot/grub2/

The file must be named in the following way:

  • grubx64.efi or grubia32.efi (for Intel)
  • grubaa64.efi (for AARCH64)
  • grubppc64.efi (for PPC64)
  • grubppc64le.efi (for PPC64 LE)

Then new host with proper architecture and PXE loader (set to Grub2) can be created and provisioned. The architecture name must match patterns defined in:

https://github.com/theforeman/foreman/blob/develop/app/models/architecture.rb

REMARK: The grubppc64.efi and grubppc64le.efi are not good names for the files as these binaries are NOT EFI on IBM POWER platform. We need to rename them to *.elf files and pass the correct DHCP filename option for those architectures. Reported as #16706


Related issues 2 (0 open2 closed)

Related to Foreman - Bug #16706: Rename POWER DHCP filenames to elfResolvedActions
Is duplicate of Foreman - Bug #16734: DHCP sets incorrect server.filename for Power Clients.Duplicate09/28/2016Actions
Actions #1

Updated by The Foreman Bot over 7 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Lukas Zapletal
  • Pull request https://github.com/theforeman/foreman/pull/3878 added
Actions #2

Updated by Lukas Zapletal over 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #3

Updated by Lukas Zapletal over 7 years ago

  • Bugzilla link set to 1376191
Actions #4

Updated by Dominic Cleal over 7 years ago

  • translation missing: en.field_release set to 190
Actions #5

Updated by Lukas Zapletal over 7 years ago

  • Description updated (diff)

Updated the mkimage command, tested on POWER7.

Actions #6

Updated by Lukas Zapletal over 7 years ago

  • Related to Bug #16706: Rename POWER DHCP filenames to elf added
Actions #7

Updated by Dominic Cleal over 7 years ago

  • translation missing: en.field_release changed from 190 to 189
Actions #8

Updated by Lukas Zapletal over 7 years ago

  • translation missing: en.field_release changed from 189 to 190

Can we keep the 1.13.1 version please? The referenced issue is minor and I won't make any effort to backport it into 1.13. I am ready for commitment with helping backporting and maintaining the 1.13 branch.

Actions #9

Updated by Dominic Cleal over 7 years ago

The referenced issue will cause a behaviour change if it's applied, which means it should be fixed before this is shipped in 1.13.1 to prevent different minor versions requiring different filenames. If you wait to fix it then it'll be more of a problem than if it's changed before.

Actions #10

Updated by Lukas Zapletal over 7 years ago

  • Is duplicate of Bug #16734: DHCP sets incorrect server.filename for Power Clients. added
Actions #11

Updated by Lukas Zapletal over 7 years ago

I was not going to propose the referenced ticket for 1.13 at all. That one can wait, but this small patch allows POWER architectures.

Actions #12

Updated by Daniel Lobato Garcia over 7 years ago

  • Target version set to 1.5.2
Actions

Also available in: Atom PDF