On Thursday, December 22, 2016 at 5:32:28 AM UTC-5, Lukas Zapletal wrote: > > Hello, > > this is expected, when you select PXEGrub2 bootloader, the DHCP option > will not be pxelinux.0. >
Right... I guess I should have written that the dhcp option was as expected, I just mentioned it to ensure you all knew it was setup properly. > Our installer was recently enhanced with some support to seetup TFTP UEFI > bootloaders via Puppet, this did not get its way into 1.13 I believe. What > you really need is to copy the bootloader there from your boot partition > (you will need to install grub2-efi for red hat system), or build your own > via grub-mkimage (but this will not work with SecureBoot unless you sign > it). If your proxy is running on Ubuntu or Debian, you need to download > these from repositories (Ubuntu ones are signed, Debian are not). > I was able to copy the grub2x64.efi file from the @mediapath/EFI/BOOT/grub2x64.efi manually to /var/lib/tftpboot/grub2 and the provisioning went off with out issue. I guess I just (incorrectly) expected to see the smart-proxy use the same wget mechanism it uses for the OS Kernel files to pickup the additional bootloader files. > In the future, we want to distribute bootloaders extracted from main > distributions in a separate package. These will be the official builds > which are also signed (and work via shim). Here are initial builds, you can > use them too. > > https://lzap.fedorapeople.org/temp/foreman-bootloaders/ > <https://www.google.com/url?q=https%3A%2F%2Flzap.fedorapeople.org%2Ftemp%2Fforeman-bootloaders%2F&sa=D&sntz=1&usg=AFQjCNHvfQuGwaP2qt3ApgRyYcN-dVEydQ> > > More details at > https://groups.google.com/forum/?fromgroups#!topic/foreman-dev/kEZaJ_8COsU > Cool, thanks for the update, somehow your post to the list evaded my searches for information on the grub2 uefi booting. > > > On Mon, Dec 19, 2016 at 9:52 PM, Sean A <[email protected] <javascript:>> > wrote: > >> Hello, >> >> I just received our first UEFI only system, and so far haven't played >> with UEFI booting much. I've setup the associations between CentOS 7.2 >> Operating System and all the grub/grub2 provisioning templates, created a >> host that's using PXEGrub2, but the host will not pxeboot. The dhcp lease >> is pointing the new host to grub2/grubx64.efi instead of pxelinux.0. The >> tftpboot directory has a grub2 folder with the mac specific grub.cfg. When >> the system boots, it waits a long time and goes back to the bios boot menu >> (not grub2/pxe). The tftp server log shows a request for >> grub2/grubx64.efi, with an error for file not found. So, it's looking like >> my smart-proxy is not grabbing that file and stuffing it into the grub2 >> directory. I've turned on debug logging in the proxy and when the build is >> initiated, there does not seem to be an attempt to copy the file from >> @mediapath /EFI/BOOT/grub2x64.efi. >> >> Has anyone else encountered this? Should I simply copy this file over >> manually? >> >> Thank you kindly, >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at https://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Later, > Lukas @lzap Zapletal > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
