Error when importing OVF from VMware

Discussions related to using VirtualBox on Windows hosts.

Error when importing OVF from VMware

Postby bblackmoor » 3. Aug 2021, 20:05

I exported a OVF (and associated files) from VMware Workstation Pro. I attempted to import it into VirtualBox ("Import Appliance...") and got the error I have seen other people report.

Code: Select all   Expand viewCollapse view
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:vmware.nvme.controller).

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: ApplianceWrap
Interface: IAppliance {86a98347-7619-41aa-aece-b21ac5c1a7e6}


I then did what others have suggested, which is to edit the MF file, replacing "ElementName" with "Caption", and "vmware.sata.ahci" with "AHCI". I then updated the SHA256 value of the OVF in the MF file.

I got the exact same error.

I have attached the VBoxSVC.log file, although from what I can see, it just says the same error.

Do anyone have any suggestions? Thank you.

VBoxSVC.zip
VBoxSVC.log
(2.36 KiB) Not downloaded yet
bblackmoor
 
Posts: 11
Joined: 15. Apr 2019, 18:05

Re: Error when importing OVF from VMware

Postby bblackmoor » 3. Aug 2021, 20:47

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   Expand viewCollapse view
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   Expand viewCollapse view
      <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?
bblackmoor
 
Posts: 11
Joined: 15. Apr 2019, 18:05

Re: Error when importing OVF from VMware

Postby Martin » 3. Aug 2021, 21:16

Some time ago I saw a similar problem while trying to move a VM from vSphere 7 back to 6.7.
Do you have the possibility to change the VMware VM before exporting?
In my case I just changed the virtual controller and disk attachment to LSI Logic SAS.
Maybe this would help also in your case. LSILogicSAS is also supported in VirtualBox.
Martin
Volunteer
 
Posts: 2507
Joined: 30. May 2007, 18:05
Primary OS: Fedora other
VBox Version: PUEL
Guest OSses: XP, Win7, Linux, OS/2

Re: Error when importing OVF from VMware

Postby fth0 » 3. Aug 2021, 22:28

As stated in 5.1. Hard Disk Controllers:

VirtualBox User Manual wrote:Warning: Booting from drives attached using NVMe is only supported when EFI is used as the BIOS lacks the appropriate driver.
fth0
Volunteer
 
Posts: 2379
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...

Re: Error when importing OVF from VMware

Postby bblackmoor » 3. Aug 2021, 23:04

Martin wrote:Some time ago I saw a similar problem while trying to move a VM from vSphere 7 back to 6.7.
Do you have the possibility to change the VMware VM before exporting?


I had the same idea. I found this video, which describes changing the controller type in VMware (https://youtu.be/LubYRrhNNZc), and I'm currently in the process of exporting the SATA-fied VM to OVF again.
bblackmoor
 
Posts: 11
Joined: 15. Apr 2019, 18:05

Re: Error when importing OVF from VMware

Postby bblackmoor » 4. Aug 2021, 00:56

The VMware VM started and ran fine after SATA-fication, and it imported into VirtualBox without errors, but when trying to run it, I get FATAL: INT18: BOOT FAILURE.

Ah, well. At this point I think it will be less time and trouble to rebuild the VirtualBox machine from scratch. Unless someone has a suggestion I haven't tried, that's what I'll do.
bblackmoor
 
Posts: 11
Joined: 15. Apr 2019, 18:05

Re: Error when importing OVF from VMware

Postby fth0 » 4. Aug 2021, 01:57

Please provide a (zipped) VBox.log file from a VM run with the INT18 message. IIRC, this message indicates that no boot drive is available, in contrast to a boot disk missing.
fth0
Volunteer
 
Posts: 2379
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...

Re: Error when importing OVF from VMware

Postby bblackmoor » 4. Aug 2021, 02:15

fth0 wrote:Please provide a (zipped) VBox.log file from a VM run with the INT18 message. IIRC, this message indicates that no boot drive is available, in contrast to a boot disk missing.


Okeedoke. I don't see anything helpful in it, but maybe you will. Thanks for offering to look into it.
Attachments
VBoxSVC.zip
(1.63 KiB) Downloaded 1 time
bblackmoor
 
Posts: 11
Joined: 15. Apr 2019, 18:05

Re: Error when importing OVF from VMware

Postby scottgus1 » 4. Aug 2021, 03:10

Try that again, please, that's the global VboxSVC.log, not the VM's vbox.log that fth0 needs.
scottgus1
Site Moderator
 
Posts: 12974
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Error when importing OVF from VMware

Postby bblackmoor » 4. Aug 2021, 03:23

scottgus1 wrote:Try that again, please, that's the global VboxSVC.log, not the VM's vbox.log that fth0 needs.


Ah, okay. Here you go. This one is a lot more complicated. Nothing here jumps out at me, but I don't really know what I am looking for. Thanks.
Attachments
VBox.zip
(24.38 KiB) Downloaded 2 times
bblackmoor
 
Posts: 11
Joined: 15. Apr 2019, 18:05

Re: Error when importing OVF from VMware

Postby fth0 » 4. Aug 2021, 11:06

In the VM configuration, the SATA/AHCI controller has 30 ports, and the virtual hard disk is attached to AHCI port 1. This is somewhat unusual, but the unused AHCI port 0 seems to create no problem:

The VirtualBox legacy BIOS has successfully read the 1st sector from the virtual hard disk, which contains the MBR. The Windows 10 MBR code (Windows™ 7, 8/8.1 or 10 MBR) checks if any of the partition table entries is marked as bootable, and if none is bootable, it executes INT 18.

If the virtual hard disk is partitioned with GPT instead of MBR, the GPT protective partition table entry in the GPT Protective MBR will not be marked as bootable. VirtualBox can only boot GPT partitioned disks from within its (U)EFI BIOS => System > Motherboard > Enable EFI.
fth0
Volunteer
 
Posts: 2379
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...

Re: Error when importing OVF from VMware

Postby bblackmoor » 4. Aug 2021, 15:20

fth0 wrote:In the VM configuration, the SATA/AHCI controller has 30 ports, and the virtual hard disk is attached to AHCI port 1. This is somewhat unusual, but the unused AHCI port 0 seems to create no problem:

The VirtualBox legacy BIOS has successfully read the 1st sector from the virtual hard disk, which contains the MBR. The Windows 10 MBR code (Windows™ 7, 8/8.1 or 10 MBR) checks if any of the partition table entries is marked as bootable, and if none is bootable, it executes INT 18.

If the virtual hard disk is partitioned with GPT instead of MBR, the GPT protective partition table entry in the GPT Protective MBR will not be marked as bootable. VirtualBox can only boot GPT partitioned disks from within its (U)EFI BIOS => System > Motherboard > Enable EFI.


Wow! That made it work! Thank you for your effort and expertise. :)
bblackmoor
 
Posts: 11
Joined: 15. Apr 2019, 18:05


Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: No registered users and 39 guests