VMware Cloud Community
sprotsman
Contributor
Contributor

Invalid value '1.0' for attribute 'version' on element 'Envelope'

I have an OVF from VirtualBox that I want to import into VMware Workstation 6.5.2 (linux). The first thing I noticed was that there is no 'Import' option in the File menu of VMware 6.5.2 for linux. So, I ran the ovf file through ovftool. ovftool reported an error when converting:

~/tmp] ovftool foo.ovf ~/tmp/convert/foo.vmx

Opening OVF source: foo.ovf

Warning: No manifest file

Opening VMX target: foo.vmx

Error:

- Line 2: Invalid value '1.0' for attribute 'version' on element 'Envelope'.

~/tmp]

This particular OVF was created with VirtualBox 2.2.4. Both support ovf 1.0, right? Output of line 2 ...

~/tmp] sed -n 2p foo.ovf

Ideas?

0 Kudos
4 Replies
admin
Immortal
Immortal

sadly virtualbox don't produce very good OVFs (in terms of OVF 1.0 std).

In this thread I have tried to explain some of the things you can do to import OVFs from VirtualBox with ovftool or other VMware OVF consumers.

but you are welcome to post the OVF and I can take a look at what's needs to be done. You could also try to contact the virtualbox team to hear what the status are on OVF support.

eske

0 Kudos
sprotsman
Contributor
Contributor

Eske,

Excellent info. I went back and exported the VBox ovf using legacy 0.9 format, changed the xml line relating to the sound card device and it ran through ovftool just fine. I just downloaded VBox 3.0 for my Mac and linux workstations and will try again with that version to see if there is any difference.

0 Kudos
admin
Immortal
Immortal

I just had a look at the 1.0 OVFs produced by VirtualBox 3.0 and they are still very very far from being OVF 1.0 spec compliant.

So I would still go with 0.9 OVFs and make the changes that are needed to import them with VMware ovftool.

eske

0 Kudos
sprotsman
Contributor
Contributor

Indeed. What a mess. I exported an ovf using VBox 3.0 and ran it through ovftool and got some nasty output:

] ovftool akm.ovf vmware/akm.vmx

Opening OVF source: akm.ovf

Warning: No manifest file

Opening VMX target: vmware/akm.vmx

Error:

- Line 8: Unsupported value 'http://www.vmware.com/specifications/vmdk.html#sparse' for attribute 'format' on element 'Disk'.

- Line 33: Unsupported element 'Description'

- Line 41: Unsupported element 'Description'

- Line 44: Unsupported element 'AllocationUnits'

- Line 50: Unsupported element 'Description'

- Line 53: Unsupported element 'ResourceSubType'

- Line 54: Unsupported element 'Address'

- Line 59: Unsupported element 'Description'

- Line 62: Unsupported element 'AutomaticAllocation'

- Line 63: Unsupported element 'AddressOnParent'

- Line 70: Unsupported element 'ResourceSubType'

- Line 71: Unsupported element 'AutomaticAllocation'

- Line 72: Unsupported element 'Connection'

- Line 77: Unsupported element 'Description'

- Line 80: Unsupported element 'Address'

- Line 85: Unsupported element 'Description'

- Line 88: Unsupported element 'HostResource'

- Line 89: Unsupported element 'Parent'

- Line 90: Unsupported element 'AddressOnParent'

- Line 95: Unsupported element 'Description'

- Line 98: Unsupported element 'AutomaticAllocation'

- Line 99: Unsupported element 'Parent'

- Line 100: Unsupported element 'AddressOnParent'

I'll stick to 0.9 legacy for now. Hopefully they can get this sorted. I'll post it to their user community too. Thanks for your help, Eske.

0 Kudos