I looked a bit deeper into things. I currently see several ways to address this:
- User is forced to figure out and to go into UEFI firmware and configure system to prioritize booting from disk over EFI shell - Set the boot order using "efibootmgr", requires us to first boot /somehow/ /something/ (this is what most distros, including ubuntu, do) - Utilize the startup.nsh fallback, either every time or for a first boot and then set things straight with efibootmgr - some other option that I'm currently not aware of I see this as a general issue. Not only does the default setup as created by virt-manager exhibit this behaviour, it's also the default firmware behaviour for x86_64 embedded systems like the MinowboardMax, Minnowboard and FRI2. While you can set the boot priority on those through the firmware menu, it will reset itself, at least on the Max, if it ever boots without the boot media. 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. The script allows for variables, so it is possible to make it start the right binary without knowing the filesystem identifier or UUID in advance. ** 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 -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
