11503 2017-05-11 22:37:18 +0000 iso image not booting in EFI mode 2017-06-27 00:11:01 +0000 1 1 11 Runtime Installation Installation unspecified x86 Multiple RESOLVED FIXED Medium+ normal 2.4 M1 1 california.l.sullivan california.l.sullivan kevin.tian sgw --- --- No (bug/feature does not impact docs) oldest_to_newest 73221 0 california.l.sullivan 2017-05-11 22:37:18 +0000 Since we're in EFI mode it falls back to the bootloader specified by EFI_PROVIDER. With systemd-boot, we get the prompt "Reboot into firmware interface" and nothing else. With grub-efi, we get the grub command line interface with no boot targets. Looking at the secondary EFI partition used in EFI mode, it looks like there is no bootloader configuration added: [clsulliv@clsulliv clsulliv]$ ls mnt2/ EFI initrd startup.nsh vmlinuz Compared to the primary partition used in legacy mode: [clsulliv@clsulliv clsulliv]$ ls mnt/ EFI efi.img initrd isolinux loader rmc.db rootfs.img startup.nsh vmlinuz Copying the loader directory from the primary partition into the secondary partition, I was able to boot in EFI mode. An easy way to reproduce is by adding meta-intel to your bblayers, setting MACHINE to intel-corei7-64, building core-image-minimal, then run the following: runqemu core-image-minimal intel-corei7-64 iso ovmf 73422 1 california.l.sullivan 2017-05-22 19:50:18 +0000 Patch sent for the systemd-boot side. After more investigation, grub might be broken in a different way, as grub.cfg already exists in the ISO's secondary partition. 74357 2 california.l.sullivan 2017-06-19 23:29:59 +0000 Patch for systemd-boot merged to master. Awaiting backport to pyro now. http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=1431210bb0f76743a631967cead87a6f1a09d070 Going to open a new bug specifically for grub, as that one appears to be a different issue that will take more investigation.