Hide Forgot
Description of problem: When I install Fedora in VM with UEFI using OVMF, it creates menu entry "Fedora" that points to \EFI\fedora\shim.efi. Installer also creates fallback file in \EFI\BOOT\GRUBX64.EFI which is used when I lose efivars or when "Fedora" menu entry is deleted. On real hardware, choosing to boot from this disk automatically looks for this file and runs it. It creates menu entry "Fedora" again (if it doesn't exist) and then shows Fedora's GRUB. In VM with OVMF, choosing to boot from this disk (or manually choosing to boot this file) freezes the computer. Note that booting from this location (\EFI\BOOT\GRUBX64.EFI) from CD works without problem (otherwise it wouldn't boot from CD at all). See reproducer here: https://jsedlak.fedorapeople.org/uefi2.webm Version-Release number of selected component (if applicable): edk2-ovmf-20160418gita8c39ba-5.fc24.noarch edk2.git-ovmf-x64-0-20161020.b2209.g8e947c0.noarch How reproducible: Always. Steps to Reproduce: 1. Install Fedora in VM using UEFI. 2. Reboot, press Escape during POST to get to OVMF's menu. 3. Choose Boot Maintenance Manager -> Boot From File, select disk, path \EFI\BOOT\GRUBX64.efi Actual results: It freezes. Expected results: It should show GRUB.
It looks like it's actually caused by shim: https://bugzilla.tianocore.org/show_bug.cgi?id=189