> 2. grub suck at booting xen.efi (or rather: xen.efi is rather picky > about its environment). On many systems, booting xen.efi without grub > (using rEFInd, EFI shell, or simply by renaming it over BOOTX64.efi) > helps with boot problems. An idea: do not use grub on UEFI installation. > Downside: you loose boot menu - no way to choose or not media > verification, or rescue mode. And no way to adjust boot arguments, > needed on some platforms to workaround UEFI bugs... To do that, you'd > need to edit EFI/BOOT/xen.cfg using some other means. > Alternative: keep grub there, but provide an instruction how to boot > xen.efi directly, in short: > > mount /dev/sdb1 /mnt # assuming /dev/sdb1 is installation USB > mv /mnt/EFI/BOOT/xen.efi /mnt/EFI/BOOT/BOOTX64.efi > mv /mnt/EFI/BOOT/xen.cfg /mnt/EFI/BOOT/BOOTX64.cfg > umount /mnt > > After such operation, media verification would fail, obviously. > > Any input on the above?
I'm currently adding EFI_LOAD_OPTION support to Xen upstream to be able to set boot entries directly with efibootmgr: https://lists.xen.org/archives/html/xen-devel/2018-01/msg00315.html. Version 3 of the patch will be sent shortly. The patch can be backported, to earlier versions of Xen as needed. With this patch in place there is no need for GRUB and you can directly pick which section you want to activate from xen.cfg using the firmware boot selection menu. The only downside is that only UEFI firmware that adheres to 2.5c or later supports it. Tamas -- You received this message because you are subscribed to the Google Groups "qubes-devel" 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/CABfawh%3D20J-bs-%3DRxc_0-BBueEKaqGtvwgXar0uybBXDvtE2uw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
