I am trying to kickstart multiple versions of Linux. Some of my systems
are BIOS based, and some are UEFI based.
I have a stanza in my dhcpd.conf file that looks like this:
class "pxeclients" {
match if substring (option vendor-class-identifier, 0, 9) =
"PXEClient";
next-server 172.31.100.1;
if option architecture-type = 00:07 {
filename "shim.efi";
} else {
filename "pxelinux.0";
}
}
I got the shim.efi I am serving from the tftpboot directory from the
Fedora 38 shim-x64 package.
The problem is, when I try to kickstart a RHEL machine, it errors out
saying the shim is invalid.
Is it that the shim.efi file is signed for UEFI environments, and the
RHEL kernel is expecting the signature for the RHEL shim.efi file? If
so, how do I specify which shim.efi file I want to use based on the
kernel? I would assume I'd need to add the correct shim.efi file in
/var/lib/tftpboot/images/[kickstart_os] the same as I add the vmlinuz
and initrd.img. But how do I tell the machine being kickstarted where to
get the correct shim.efi? Is there a vendor-class-identifier I can check
to see what the OS is, and then point the machine being kickstarted to
that file?
Or am I going about this the wrong way?
Thomas
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
