OVA” file with VMware’s “ovftool

Asked By romasfleeman 40 points N/A Posted on - 02/24/2013

I have VMware Workstation 7.1 running on a 64-bit open SUSE 11.3 system. I built a 32-bit open SUSE 11.3 guest machine on another VMware, then I converted it to an "OVA" file with VMware's "ovftool". znmeb@AlgoCompSynth: ~/vmware/Project Kipling VMware > ovftool — targetType= OVA Project Kipling VMware.vmx . Opening VMX source: Project Kipling VMware.vmx Opening OVA target: . Writing OVA package: Project Kipling VMware.ova Disk progress: 2% Disk Transfer Completed successfully znmeb@AlgoCompSynth:~/vmware/Project Kipling VMware > When I tried to import the resulting OVA file into VirtualBox 4.0.0. That didn't work – I got an error (screenshot attached).

VirtualBox – Error

Failed to import appliance /home/znmeb/vmware/Project Kipling VMware/Project Kipling VMware.ova Error reading " / /home/znmeb/vmware/Project Kipling VMware/Project Kipling VMware.ova: Unknown resource type 1 in hardware item, line 105

• Status: Open
• Question Views: 1802
• Answer Count: 2
• Vote Up 0 Vote Down

• Answer Accepted: Yes
• Question Category: VMware

Best Answer by Drake Vivian

Go To Solution

Best Answer

Best Answer

Answered By Drake Vivian 30 points N/A #137737

OVA” file with VMware’s “ovftool

Hi there Romasfleeman,

 

First of all, you are using quite an old version of the software so the update would be really useful. 

 

In case that even after the update you can't open the file, there are a few simple workarounds.

 

Ovftool has a really great commandline that will turn errors into warnings and let you work with no breakdowns. Just enter a lax command line to avoid the error. 

 

You can also try changing the line with the problem to:

 

<vssd:VirtualSystemType>vmx-06</vssd:VirtualSystemType>

 

Hope this helped,

Drake Vivian

About Drake Vivian

Questions
0

Answers
820

Best Answers
186

• Vote Up 0 Vote Down

• Posted on - 03/19/2013
• Question Category: VMware

Answered By Waters Magner 5 points N/A #199153

OVA” file with VMware’s “ovftool

It seems as if you are using the old version of the ovf tool. You need to upgrade yourself. You need to install a newer version of the ovf tool. You can try ovf 2.0.1. You can turn the errors into warnings with the code:

ovftool has a –lax commandline option which turns errors into warnings.

Through this code you will be able to test whether the other part of the code is working fine or note. Hope that will solve the issue.

About Waters Magner

Questions
0

Answers
199

Best Answers
32

• Vote Up 0 Vote Down

• Posted on - 11/19/2013
• Question Category: VMware