VERR_NOT_SUPPORTED adding vmdk

[frogola]

I created a vmdk from a Windows 7 physical machine using vmware p2v. When I create a new virtualbox and select this file for the disk I get the following error:

Failed to open the hard disk /Users/joeblow/vms/sfdhqmislt56v/sfdhqmislt56v-disk1.vmdk.

Could not get the storage format of the medium '/Users/joeblow/vms/sfdhqmislt56v/sfdhqmislt56v-disk1.vmdk' (VERR_NOT_SUPPORTED).

Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: Medium
Interface: IMedium {29989373-b111-4654-8493-2e1176cba890}
Callee: IVirtualBox {3b2f08eb-b810-4715-bee0-bb06b9880ad2}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

When I try importing the ovf I get the following:

Failed to import appliance /Users/joeblow/vms/sfdhqmislt56v/sfdhqmislt56v.ovf.

Could not open the medium storage unit '/Users/joeblow/vms/sfdhqmislt56v/sfdhqmislt56v-disk1.vmdk'.

VMDK: incorrectly quoted value in descriptor in '/Users/joeblow/vms/sfdhqmislt56v/sfdhqmislt56v-disk1.vmdk' (VERR_VD_VMDK_INVALID_HEADER).

VD: error VERR_VD_VMDK_INVALID_HEADER opening image file '/Users/joeblow/vms/sfdhqmislt56v/sfdhqmislt56v-disk1.vmdk' (VERR_VD_VMDK_INVALID_HEADER).

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: Appliance
Interface: IAppliance {3059cf9e-25c7-4f0b-9fa5-3c42e441670b}

The vmdk boots successfully on vmware esxi 5.1. Any idea why vb 4.2.10 chokes on 'incorrectly quoted value in descriptor'? Any way to figure out which descriptor it doesn't like? Anyone ever seen this before?

Thank you for your attention.

[ChipMcK]

File --> Import Appliance ... is for appliances that have been exported File --> Export Appliances ....

You need to create a virtual machine Machine --> New ... and attach the .vmdk file to it as its virtual drive/disk

It is helpful if you check the Device Manager of the original physical machine
for type of disk controller and type of disk

[frogola]

To clarify: I tried both methods [creating new vm using existing vmdk, and importing from .ovf] -- both methods fail with different errors which I pasted into my original post.

[mpack]

Forget about using the VMDK without importing it. VMDKs shipped as part of an exported appliance are typically compressed, which means they can't be used as normal VMDKs.

Concentrate on why the "import" didn't work. The error message should be a clue.

Or, you may find it easier to start again: go back to the Win7 machine and image the hard disk using Disk2VHD. Build a VM around the VHD. I assume you're aware that you'll need to reactivate your Windows license.

[frogola]

Thanks mpack, I didn't know about Disk2vhd. I will give it a try.