Red Hat Bugzilla – Bug 1458937
[RFE] Add example kickstarts for 32bit UEFI support to livemedia-creator
Last modified: 2018-04-10 13:39:17 EDT
32bit UEFI booting needs different packages on each arch, we need to add and test new examples for UEFI64/32 on x86_64, aarch64, and ppc64
Created attachment 1285163 [details] Example kickstart for 32/64 bit UEFI on x86
I've tested this kickstart with x86_64 and qemu UEFI and it works fine. I don't have any way to test 32bit booting. I added the following for x86: grub2-tools-efi shim-x64 grub2-efi-x64-cdboot efibootmgr shim-ia32 grub2-efi-ia32-cdboot aarch64 should, I think, add: efibootmgr grub2-efi-aa64-cdboot grubby shim-aa64 ppc64 should be: grub2-tools grub2-tools-minimal grub2-tools-extra grub2-ppc64 ppc64le should be: grub2-tools grub2-tools-minimal grub2-tools-extra grub2-ppc64le
*** Bug 1460499 has been marked as a duplicate of this bug. ***
Changes are smaller than I expected: https://github.com/rhinstaller/lorax/pull/216
Example kickstart is missing package grub2-efi-ia32 . System is unable to boot without it. Tested with no-virt option both make-disk with rhel7-minimal.ks and make-iso with rhel7-livemedia.ks . Adding mentioned package manually makes both .iso and .img bootable. Legacy grub2-efi in %packages is provided by grub2-efi-x64 , but not with grub2-efi-ia32 , which is not installed. I have tested both output from make-iso and make-disk .img on both x64(KVM VM) and ia32(Minnowboard Turbot) firmwares. With added package grub2-efi-ia32 it works fine. Patch in attachment.
Created attachment 1292006 [details] patch_to_add_package
Verified on RHEL-7.5-20180201.2 with lorax-19.6.104-1 . Lorax now contains rhel7-livemedia/minimal.ks with correct packageset Live .iso is able to boot without problem on 32bit UEFI firmware. All needed packages are installed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0947