virtualbox.org

I've got a pretty complicated setup, but I'll work through bringing you up to speed. Here's what my disk, /dev/sdb, looks like:
The disk is a hardware RAID virtual device. Partition 1 is unformatted space for a legacy GRUB BIOS bootloader no longer being used. Partition two is my FAT-32 EFI boot partition. (This is how I'm booting. I have rEFInd as a boot manager allowing me to switch between Windows 7 and my Linux installation on boot) Partition 3 is my main Linux filesystem. Partition 4 is the msftres partition used by Windows 7. Finally, partition 5 is the NTFS Windows boot drive. It contains Windows 7 64bit SP1. I can boot to either my Linux installation or to my Windows 7 installation on physical machine startup, so boot definitely works. GRUB BIOS boot works too, but only for Linux, as Windows 7 in installed in GPT/EFI mode.

What I'd like to do is to simply boot my Windows 7 installation on /dev/sdb5 from within my Linux operating system using VirtualBox. I've done the following to get things rolling:
That allows me to access my disks as a non-root user. Followed by a log out and a log back in...
Great, the groups modification worked. Now, let's create a raw disk file:
Cool, now, add that to the Windows 7 virtual system in the VirtualBox UI and then enable EFI booting.

Now, onto the problematic stuff...

Ok, so now that our Windows 7 64bit virtual system is ready to go, let's boot.



Ok, fine, so that's not working, so let's type "exit" and get to the console. I select "Boot Maintenance Manager," then "Boot from File," and I select "ESP:/EFI/Microsoft/Boot/bootmgfw.efi", and then I see this terrible, terrible screen:



What is this problem being caused by and how do I get around it? I feel like I'm so close to booting my Windows 7 installation from within my Linux installation.

PS: I've tried also using the Windows 7 installation CD to try and do a startup repair in case something was wrong there, but it prompts me to reinstall Windows, apparently not finding the Windows installation at all. Additionally, I've verified that it's definitely working, as it CAN boot into the rEFInd manager, but I get the same code above when I then try to boot into Windows.

As i know, VBOX EFI and Windows does not work together.

This EFI custom boot is not a Virtualbox problem and is out of scope of this forum. You would have the same issue on real hardware, therefore I don't think you'll get any support here about this.

EFI custom boot?

On my actual hardware, both booting directly from the Microsoft Windows Boot Manager and chain-loading it through rEFInd works great. This seems to definitely be a bug with the VirtualBox EFI implementation.

rfkrocktk wrote:EFI custom boot?

Possibly some missuse of the words on this one - what I meant is that I am not aware that Microsoft supports this - hence my use of the "custom" word.

rfkrocktk wrote:On my actual hardware, both booting directly from the Microsoft Windows Boot Manager and chain-loading it through rEFInd works great. This seems to definitely be a bug with the VirtualBox EFI implementation.

If your setup doesn't work only on Virtualbox, and you can reproduce all the steps precisly, feel free to submit a bug report using the bug tracker, and post back here the ticket link

Section 3.12 of the users manual.
<Snip>

Note that the VirtualBox EFI support is experimental and will be enhanced as EFI matures and
becomes more widespread. While Mac OS X and Linux guests are known to work fine, Windows
guests are currently unable to boot with the VirtualBox EFI implementation.

That said I was able to make it work but it is very nasty and not something I wish to get into. It took a lot of scripting and nasty booting with RAW and such. If you understand the process you may get it to work but I just didn't see the benefit other than seeing if it could be done. One of the biggest issues was the ISO standard that Windows used. Not the same as Mac or Linux EFI and once you figure out how to work around that the install should work.

Perryg wrote:Section 3.12 of the users manual.
<Snip>

Note that the VirtualBox EFI support is experimental and will be enhanced as EFI matures and
becomes more widespread. While Mac OS X and Linux guests are known to work fine, Windows
guests are currently unable to boot with the VirtualBox EFI implementation.

That said I was able to make it work but it is very nasty and not something I wish to get into. It took a lot of scripting and nasty booting with RAW and such. If you understand the process you may get it to work but I just didn't see the benefit other than seeing if it could be done. One of the biggest issues was the ISO standard that Windows used. Not the same as Mac or Linux EFI and once you figure out how to work around that the install should work.

Do you have any guide for getting started on it? I'd really like to get it working if at all possible.

Not really. Everything I did was by the seat of my pants. I failed more time than I succeed and as such I have no notes. Its just a frame of mind. If you want it to work and stick with it you should be able to make it work, but only if you have more than basic knowledge of UEFI/EFI. VirtualBox really had nothing to do with it. Google installing windows EFI like I did and pull in information form everywhere you can.

That said since Windows EFI was not intended to work in VirtualBox there really is no support, until the DEVs have time to make it work.

Will do. The nightmare that is EFI seems to be a recurring one.

It's amazing to me that it's so difficult to get the Windows EFI boot working. I'd assume that it'd be the most compatible boot loader out there. All UEFI motherboards don't have much trouble booting it.

I have set up my new PC with dual-boot UEFI (>2TB partitions) and I wanted to get my Windows bootable from native partition and VirtualBox .. have you been able to make it work @rfkrocktk ?