On Mon, Dec 02, 2013 at 11:07:40PM -0000, Jason Gerard DeRose wrote: > Colin, Steve, any recommendations on how to build ovmf in the way needed > to work around this?
> System76 is working toward switching all our products to UEFI, but we > use qemu for our golden image mastering and maintenance (something I'm > not keen on giving up as it's proven to be totally awesome). > I'm pretty sure I'm now stuck at this same bug. I can (seemingly) > successfully complete an install, but for the life of me, I can't then > boot from the disk image. I've tried with qemu 1.5 on Saucy, and qemu > 1.6 on Trusty (using the pre-built ovmf Ubuntu package). I've also tried > with random ovmf builds from around the net, still no luck. That doesn't sound to me like it has anything to do with the shell support. Rather, it's probably because ovmf doesn't support persistence of nvram, so you've lost the information about the EFI boot options which is stored there. You should be able to manually browse the firmware menu to boot by filename (/efi/ubuntu/bootx64.efi), but that's probably not a very maintainable solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1223413 Title: EFI Shell not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1223413/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
