Pxe with uefi katello 3.16

Hmm can you do the search and then echo $chroot? It looks like the search command is not setting the variable correctly? The last time you executed it returned it twice. I am going to test this locally in libvirt just to see if it returns the same thing.

TODO: Need to reinstall my “centos8-efi-default” VM it no longer works :slight_smile:

Want to try Oracle Linux, can you give me hint where do I find kickstart repository? I mean the yum repository which contains PXE files.

Is SecureBoot enabled or disabled? Can you try without SecureBoot?

Also, it works for me. These lines boots the grub2:

chainloader (hd0,gpt1)/EFI/redhat/grubx64.efi
boot

That’s exactly what the teamplate does. Try this yourself, edit the template in /var/lib/tftpboot/grub2/grub.cfg-MAC_ADDRESS to this contents. Our default template is little bit more complex - it tries to find different OSes… but it does the same thing.

i didn’t get you . you mean pxe files for vmlinuz and kernel?

I don’t use secure boot.

do i have tor change both grub.cfg-$MAC files?

[root@ol07stl00 grub2]# ll -lrt | grep -i f6
-rw-r–r-- 1 foreman-proxy foreman-proxy 5539 Sep 1 17:29 grub.cfg-01-00-50-56-8d-85-f6
-rw-r–r-- 1 foreman-proxy foreman-proxy 5539 Sep 1 17:29 grub.cfg-00:50:56:8d:85:f6

One of these which I don’t remember is relevant for your version. So probably both.

But your chainloader command does not work, which is weird. It works for me. I am out of ideas. I asked our grub2 engineer but I can’t reproduce this so I can’t help you.

Hello,

I bump on this issue too …

Works fine with vmware 6.5 but fails on vmware 7 (foreman 3.2).
Same debug done and no clue to explain this …

Any new idea ?

Regards

Hey @lovi

It would be really best if you typed up a full report on your own scenario and your own specific versions of everything, thank you

Here more details to report :
guestOS : rhel 8.5
Foreman 3.2
vmware 7
templates used : PXEGrub2 UEFI

The guest build is Ok and it goes to net boot with the pxegrub2_chainload which fails :
error: ../../grub-core/commands/search.c296:no such device:
if i change the boot order to disk : system boot is Ok
if i test in grub shell everything is fine looks ok but cant boot.
if i do a build of a guest on vmware 6.5 : chainload is Ok and system boot.

Sorry for the delay, this is a known issue in VMWare’s QuickBoot feature that was enabled by default in v7. Red Hat engineers are already working on a workaround for Grub2, it will be part of the next Fedora/RHEL versions, upstream users need to wait a bit longer as its slower to get patches in. Debian/Ubuntu users as well, in that case report this to those OSes to get patches in.

We are implementing a warning that will show up on the screen so people are aware:

echo "VMWare hosts with QuickBoot feature enabled may not find the local ESP"
echo "partition due to not initializing all the EFI devices. To workaround, upgrade"
echo "to the latest grub2 (*) and uncomment "connectefi scsi" statement in the"
echo "grub2_chainload template."
echo
echo "Virtual or physical hosts using Software RAID for the ESP partition may try"
echo "booting on the Software RAID, which will fail. To workaround, upgrade to the"
echo "latest grub2 (*) and add "--efidisk-only" argument to the "search" command in"
echo "the grub2_chainload template."
echo
echo "(*) grub2-efi-x64-2.02-122.el8 (upstream doesn't have the patches yet)"

@MariaAga

1 Like

Thanks for this callback, here is some news :

  • I upgrade to rhel8.6 which contains (grub2-efi-x64-2.02-123.el8.x86_64) , i keep foreman 3.2
  • vmware guest build results :
  • rhel 7.9 , 8.6 build, chainload, boot ok (vmware 7, 6.7) with original chainload_grub2 template without “–efidisk-only”.
  • rhel 8.4, 8.5 build, chainload, boot ok (vmware 7, 6.7) with original chainload_grub2 template without “–efidisk-only”. But i must add “efi.quickBoot.enabled = FALSE” in compute_attributes.extra_config. (Unable to install RHEL 8 on VMWare compatibility: ESXi 7.0 U2 and later (VM version 19) - Red Hat Customer Portal)

So there was two issues for me in this install process.

1 Like