Looking through the OVF file, I found a section that referred to "vmware.nvme.controller". Thinking this might be a similar case to the AHCI entry, I changed that to "NVMe". I then got this error:
Code: Select all
Failed to import appliance F:\VMware_VMs\export\Windows 10 PCCW Global.ovf.
Error reading "F:\VMware_VMs\export\Windows 10 PCCW Global.ovf": Host resource of type "Other Storage Device (20)" is supported with SATA AHCI controllers only, line 47 (subtype:NVMe).
Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: ApplianceWrap
Interface: IAppliance {86a98347-7619-41aa-aece-b21ac5c1a7e6}
That section, by the way, looks like this:
Code: Select all
<Item>
<rasd:Address>0</rasd:Address>
<rasd:Description>NVME Controller</rasd:Description>
<rasd:Caption>nvmeController0</rasd:Caption>
<rasd:InstanceID>3</rasd:InstanceID>
<rasd:ResourceSubType>vmware.nvme.controller</rasd:ResourceSubType>
<rasd:ResourceType>20</rasd:ResourceType>
</Item>
Apparently VirtualBox does not like NVMe as ResourceType 20. Looking at this...
https://www.vmware.com/pdf/ovf_spec_draft.pdf ... I see no other ResourceType for a non-IDE controller, so I tried deleting the NVMe section, updated the parent ID of the hard drive to point to the AHCI controller (which I don't expect to actually work, but I am just trying anything at this point), and recalculated the SHA256 value.
That appeared to work. The "Import" summary displayed, and VirtualBox began the process of converting the VMDK file to a VDI file. When it finished, I started up the VM... and got
FATAL: INT18: BOOT FAILURE. Which I expected.
I then edited the settings on the VM, adding a NVMe controller (why can I add one but not import one? I have no idea.), and moving the VDI file from the SATA/AHCI controller to the NVMe controller. I started up the VM... and got
FATAL: Could not read from the boot medium! System halted.
Any suggestions?