So after doing some deep digging and researching countless articles all over the internet, I found the solution right on the Qubes OS’s UEFI troubleshooting page and I was finally able to successfully boot the system. So I followed the guide to create a xen.cfg file and fill it with the current values. Then using this guide which was also suggested by you, I got to the point where the boot entry was visible in the boot menu, but after starting it ended up with a no kernel image found error. So I copied the vmlinuz kernel and initramfs files to mnt/efi/EFI/BOOT. And when I rebooted it started to load the OS. So then I decided to make an efi entry for the grub bootloader (since grub.efi, grub.cfg where in the BOOT folder) and to my surprise grub did show up and loaded by default. Interesting thing is if I decide to remove BOOTX64.efi entry with efibootmgr -b <boot order number> -B and its related files, grub doesn’t work. So I have to keep both the entries in order to start QubesOS.
I might try your latest suggestion to check if I can start with just the grub entry. Thanks for your help and you have been a great!
1 Like