1. Via Disk2VHD, converting the .VHDX image to .VDI through virtualboxmanage.
Then loading the .VDI file to a new instance choosing the "Use an Existing Virtual Hard Disk File" option enabling EFI (special OSes only).
Done this at start the virtual machine drops on Shell
Code: Select all
UEFI Interactive Shell v2.2
EDK II
EFI v2.70 (EDK II, 0x00010000)
Mapping table
BLK0: Alias(s):
PciRoot(0x0)/Pci(Ox1F,0x2)/Sata(0x0,0XFFFF,0x0)
Press ESC in 1 seconds to skip startup.nsh or any other key to continue.
Shell>
No change, it stays on Shell.
2. Using Raw Disk Access:
- I copy all related Windows installation partitions on a separate drive with GParted
- Make a .VMDK file following section 9.7.1.2. of Virtualbox manual makign sure to identify the correct partitions for boot and data.
- for some reason the .VMDK does not get read (VERR_ACCESS_DENIED). Among the possible causes of this there is data corruption. I run file system check/repair on Windows before doing all this.
Code: Select all
Result Code:
VBOX_E_FILE_ERROR (0X80BB0004)
Component:
MediumWrap
Interface:
IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}
Callee:
IVirtualBox {7682d5eb-f00e-44f1-8ca2-99d08b1cd607}
Callee RC:
VBOX_E_OBJECT_NOT_FOUND (0X80BB0001)
- I start the virtual machine
Code: Select all
BdsDxe: loading Boot0001 “UEFI VBOX HARDDISK VB892112c4-e3d579aa “ from PciRoot(0x0)/Pci(0xD, 0x0)/Sata(0x0,0xFFFF,0x0)
BdsDxe: starting Boot0001 “UEFI VBOX HARDDISK VB892112c4-e3d579aa “ from PciRoot(0x0)/Pci(0xD, 0x0)/Sata(0x0,0xFFFF,0x0)
error: unknown filesystem.
Entering rescue mode...
grub rescue>
Now, Windows 11 was a fresh install so I needed to have an .ISO. As for existing Windows migration in none of the guides I followed I seem to remember the use of a .ISO image to boot what is in .VDI/.VMDK but I suspect I may need one.
Any ideas?