Dears,
This is a tought one for me to crack, and probably someone here is better than me. I am running a computer with three physical disks, one of which contains the Windows operating system along with EFI bootloader, one contains a Fedora installation AND its EFI partition AND EFI bootloader. One is just sitting there, spinning around.
The disk with Windows is what my firmware boots to by default. It uses the EFI partition on that disk and fires up Windows. The disk with the Fedora installation does not contain any partitions mounted in Windows, and, in fact, the only partition readily recognized by Windows is the EFI partition. The remaining partitions are EXT4.
The Fedora disk is also directly bootable, if I choose a different boot device. It is also used as a virtual disk in a VirtualBox guest through raw disk access. Since nothing is mounted there, it should be a piece of cake. And it is.
Except for the EFI partition on that disk. I can read it but I cannot write to it. Windows, the host OS, is preventing the guest from doing so. Of course, only while running the Fedora installation via VirtualBox. If running directly, no problem. This presents the problem that if I update the kernel in the guest, I cannot update the bootloader in the EFI partition because I cannot write to it.
I have tried running VirtualBox from an elevated command prompt, I have tried runasing it as SYSTEM, and I have tried every other conceivable thing. No luck. In Windows 7, this same setting worked perfectly.
Can someone help me help my Windows to ignore the fact that there is an EFI partition on the second disk and just let VirtualBox play around with the disk as much as it wants?
Thank you.
--
Mikko
This is a tought one for me to crack, and probably someone here is better than me. I am running a computer with three physical disks, one of which contains the Windows operating system along with EFI bootloader, one contains a Fedora installation AND its EFI partition AND EFI bootloader. One is just sitting there, spinning around.
The disk with Windows is what my firmware boots to by default. It uses the EFI partition on that disk and fires up Windows. The disk with the Fedora installation does not contain any partitions mounted in Windows, and, in fact, the only partition readily recognized by Windows is the EFI partition. The remaining partitions are EXT4.
The Fedora disk is also directly bootable, if I choose a different boot device. It is also used as a virtual disk in a VirtualBox guest through raw disk access. Since nothing is mounted there, it should be a piece of cake. And it is.
Except for the EFI partition on that disk. I can read it but I cannot write to it. Windows, the host OS, is preventing the guest from doing so. Of course, only while running the Fedora installation via VirtualBox. If running directly, no problem. This presents the problem that if I update the kernel in the guest, I cannot update the bootloader in the EFI partition because I cannot write to it.
I have tried running VirtualBox from an elevated command prompt, I have tried runasing it as SYSTEM, and I have tried every other conceivable thing. No luck. In Windows 7, this same setting worked perfectly.
Can someone help me help my Windows to ignore the fact that there is an EFI partition on the second disk and just let VirtualBox play around with the disk as much as it wants?
Thank you.
--
Mikko
