I have a physical Windows 10 machine that I'm trying to convert to a VM. I have a terabyte partition that is about 80% full. I regularly run the Windows 7/8 backup utility, which creates a complete VHDX once a week. I grabbed the VHDX, copied it to a Linux system, converted it to a VDI, attached it to a VirtualBox VM, and tried to boot. I immediately get "FATAL INT18 BOOT FAILURE". It is so quick that I can't even press F12 to boot into the fake BIOS.
Now, this question has been asked many times before, as I have learned through a week of screwing around with this, but the solution here does not help: VirtualBox FATAL: INT18: BOOT FAILURE
Here are my futile efforts so far.
I can mount the VDI on the host system with "vboximg-mount". I see two partitions. If I mount the second partition, the data is there in all its glory. (The first partition is a 100MB Windows special partition.)
I can boot the VM with a rescue CD.
lsblkshows both partitions. If I mount the second partition (/dev/sda2), the data is there in all its glory.I tried setting the VM to "EFI" mode. It boots to the EFI shell, which shows BLK devices for the SATA controller and the two partitions, but there are no FS devices, as if it doesn't find a file system.
I tried changing the partition table to MBR instead of GPT, and marking the second partition as bootable. No change. I've toggled back and forth several times.
I tried copying an EFI setup into /boot/efi including
bootx64.efi. No change. Again, the EFI shell doesn't find a file system.
I'm just about out of ideas. I've done lots of VMs before, and I don't like to be defeated by inanimate objects. It seems like everything is in order, but no joy. Any suggestions or hacks are welcome.
