Description of problem:
In x86_64 images up to and including 17 Alpha TC2, EFI booting in VirtualBox worked, sort of (although graphical anaconda didn't, leading to text install - see bug 742695). However, in 17 Alpha RC1 and later, EFI booting in VirtualBox leads to a grub prompt. This happens on x86_64 DVD, netinst, and Live images. I'm currently using VirtualBox 4.1.14 from the Oracle repo.
I realize that VirtualBox is proprietary and that EFI seems to work on most real hardware, but it would be nice to establish for certain that Fedora isn't doing something to cause it. I have no EFI hardware, so unless support is added to KVM or some other virtualization tool, I'm unable to test EFI.
See also my comments in bug 816410, which was closed due to EFI working in most real hardware.
(In reply to comment #0)
> I realize that VirtualBox is proprietary
It's Open Source (GPLv2), not proprietary, sorry.
Macs are no longer EFI booting Live Desktop either.
Same with 18 Alpha TC1 and VirtualBox 4.1.18.
Don't know when the behavior changed, but with 18 Alpha TC6 and VirtualBox 4.1.22, I get a Grub2 menu with two entries, "Fedora 18-Alpha-TC6" and "Test this media & start Fedora". Choosing either one gives "Secure boot not enabled", then after a long wait, it boots and finally drops to emergency mode. Attaching screenshots below.
Created attachment 611279 [details]
end result of booting "18-Alpha-TC6"
Created attachment 611280 [details]
Test this media & start Fedora
end result of booting "Test this media & start Fedora"
Should also mention that this looks similar to bug 849389 except no mention of dropping to emergency mode there.
This appears to be fixed now - in recent 64-bit install images, EFI boots although X startup fails (bug 742695).