Hello,
I am new to OVFTool and am having difficulty using it in Terminal on my MacBook Pro to convert an OVA (created by exporting my WinXp virtual machine from within VirtualBox), to a VMX file for use in VMWare Fusion on my MacBook Pro.
I have installed the OVFTool on my boot drive (partition) which is named "LFP OS", in the folder: /Library/VMWare/OVFTool/.
I have the OVA file on my data drive (partition) which is named "LFP Data" in the folder: /Virtual Machines/WinXP.ova.
I want to create a virtual machine file (VMX) in the same location as the soure that I can then import into VMWare Fusion. I have gone through the OVFTool User Guide, forums, Google etc. and cannot get it to work properly. It may be as simple as my Terminal syntax being off. Anyway, please help.
Here is what I used in Terminal:
LFP-MacBook-Pro:virtual machines nils$
LFP-MacBook-Pro:virtual machines nils$ pwd
/volumes/lfp data/virtual machines
LFP-MacBook-Pro:virtual machines nils$ ./Volumes/LFP\ OS/Library/VMWare/OVFTool/ovftool /Volumes/LFP\ Data/Virtual\ Machines/WinXP.ova /Volumes/LFP\ Data/Virtual\ Machines/WinXP.vmx
-bash: ./Volumes/LFP OS/Library/VMWare/OVFTool/ovftool: No such file or directory
LFP-MacBook-Pro:virtual machines nils$
Thanks for your time!
Regards,
SBNL
I have had some success but ran into this error:
LFP-MacBook-Pro:virtual machines nils$ /Volumes/LFP\ OS/Library/VMWare/OVFTool/ovftool /Volumes/LFP\ Data/Virtual\ Machines/WinXP.ova /Volumes/LFP\ Data/Virtual\ Machines/
Opening OVA source: /Volumes/LFP Data/Virtual Machines/WinXP.ova
Opening VMX target: /Volumes/LFP Data/Virtual Machines/
Error: OVF Package is not supported by target:
- Line 25: Unsupported hardware family 'virtualbox-2.2'.
LFP-MacBook-Pro:virtual machines nils$
I have searched the forums and have found nothing current on this problem. I may try some other export options from within VirtualBox.
Is there not a simple and straightforward way to get from VirtualBox to VMWare Fusion?
Thanks,
SBNL
The simple solution is to use the --lax option.
eske
--lax would be simple if it worked ![]()
It doesn't always work.
In my case I had three errors/warnings and a vmx was generated but no vmdk, ovftool basically ignored the disk file. No surprise trying to start the vmx resulted in an OS not found error. ![]()
ova is tar archived, so first thing I tried was to run the ova though tar:
taf xvf machine.ova
This extracts two files, a .vmdk and a .ovf. The .ovf can now be edited to get around errors.
I had three errors:
- Line 25: Unsupported hardware family 'virtualbox-2.2'.
- Line 66: OVF hardware element 'ResourceType' with instance ID '5': No support for the virtual hardware device type '20'.
- Line 92: OVF hardware element 'ResourceType' with instance ID '8': No support for the virtual hardware device type '35'.
Reading the ovf it seemed like line 66 was the culprit, since it related a sata driver. I came across a post http://labs.consol.de/lang/de/blog/nagios/wenn-der-esx-server-keine-icinga-vm-annimmt/ which suggests changing that to scsi. Did that, reran ovftool (using --lax still to get around the other errors) and it processed the vmdk.
Double clicking the vmx this time resulted in a booted vm, and I'm now about to install vmware tools.
HTH
Thanks for the info.
Would it be possible for you to send me the OVF (just the OVF and not the disk)
so I can take a look on it and provide a better --lax option for the next version of ovftool?
eske
I've attached both the original and my modified version of the ovf.
(fwiw it's from the Drupal quickstart vm, http://drupal.org/project/quickstart )
