On Mon, May 18, 2015 at 11:08:25AM -0000, Thomas B. Rücker wrote: > ** Attachment added: "Default machine config created by virt-manager on > ** 14.04" > https://bugs.launchpad.net/snappy-ubuntu/+bug/1425370/+attachment/4399386/+files/snappy-efi-test5.xml
This image config looks fine. The problem is still not reproducible for me. This looks like a bug in the version of OVMF.fd that you're using. Are you using the ovmf package from Ubuntu or did you build your own? > I'd personaly suggest the option of using "efibootmgr" and resolving the > first boot situation by falling back to a startup.nsh to execute > bootx64.efi. This should make the image boot out of the box on most, if > not all, hardware. That's not necessary or appropriate. You should write snappy to a boot disk. Your hardware should be configured to try to boot from that disk. How this happens is defined in the UEFI spec, and does not require any configuration of firmware variables to point to a specific path on disk - it will automatically boot from \EFI\BOOT\BOOTX64.efi, which is exactly the path we have written our bootloader to. If you're having problems getting this to work on a system that supports 64-bit UEFI, either your system's firmware is buggy, or you're installing snappy to a disk that is not configured in the firmware to be a boot disk. In the first case the firmware should be fixed to comply with the UEFI spec. In the second case, the firmware isn't looking at the disk, so making other changes to that disks contents (such as startup.nsh) won't have any effect on the system's boot behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425370 Title: "ubuntu-device-flash core" images can't boot with UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/snappy-ubuntu/+bug/1425370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
