2.1 Edit ovf file so 'rasd' elements are sorted in the following order:
<Item> <rasd:Caption>Some caption</rasd:Caption> <rasd:Description>Some description</rasd:Description> <rasd:InstanceId>0</rasd:InstanceId> <rasd:ResourceType>1</rasd:ResourceType> <rasd:ResourceSubType>2</rasd:ResourceSubType> </Item>2.2 Ensure that rasd:Parent elements precede rasd:AdressOnParent elements.
2.3 Change the extension of original vmdk disk files to something like '~vmdk'.
2.4 Check that conversion is possible using VMWare OVF Tool with the following command:
"C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" --noDisks "ODD - Source.ovf" "ODD - Source.vmx"You should see the following output:
Opening OVF source: ODD - Source.ovf Opening VMX target: ODD - Source.vmx Writing VMX file: ODD - Source.vmx Transfer Completed Warning: - No manifest file found. - No manifest entry found for: 'ODD - Source-disk1.vmdk'. - No manifest entry found for: 'ODD - Source-disk2.vmdk'. Completed successfullyIf not, the tool will report error lines. So correct errors and rerun.
2.5 Delete vmdk files generated by ovftool and change back the extension of original files.
Pitiful but OVF Tool alone cannot properly convert ovf to vmx. Disk partitions will remain read only as made by VirtualBox export process.
3. So the last thing to do is to use VMWare Converter 4.0.1 (can be downloaded following links in this post) to convert ovf to vmx changing disks types to 2 GB Split pre-allocated.
No comments:
Post a Comment