Ticket #11160 (new defect)
.ova image created with Virtual Box, failed to import in VMware
Reported by: | Tsso | Owned by: | |
---|---|---|---|
Component: | OVF | Version: | VirtualBox 4.2.4 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
The image can be imported into Virtual Box without any problems.
VMware fails:
The import failed because /home/user/Whonix-Gateway.ova did not pass OVF specification conformance or virtual hardware compliance checks. Click Retry to relax OVF specification and virtual hardware compliance checks and try the import again, or click Cancel to cancel the import. If you retry the import, you might not be able to use the virtual machine in VMware Player.
Who is responsible for the bug? VMware or Virtual Box?
VMware Bug report: http://communities.vmware.com/thread/423920
Download link Whonix-Gateway.ova: http://sourceforge.net/projects/whonix/files/whonix-0.4.5/ project website: http://whonix.sf.net
Source code: https://github.com/adrelanos/Whonix
How the .ova image is created: https://github.com/adrelanos/Whonix/blob/master/whonix_createvm
Change History
comment:5 Changed 5 years ago by Paras
It worked for me by exporting from VirtualBox as v1.0 ova and selecting "Include Manifest File" option
comment:6 Changed 5 years ago by dragon788
The correct solution to this is to export as ovf v1 either from the UI, or when running an export from the command line it appears to default to v1.
vboxmanage import futsy-v2.ova
# A vm's name can be different than the OVA name
vboxmanage list vms
# VM_NAME from listing above
vboxmanage export VM_NAME -o futsy-v1.ova
# --lax option basically tells the ovftool not to fail on errors, just make them warnings
ovftool --lax futsy-v1.ova futsy-v1.vmx
This should import and work without issue in VMware Workstation/Fusion/ESXi.
comment:7 Changed 3 years ago by Calidge
The previous comment is a workaround, not a solution.
Problem still exists. VM Workstation will import V1 spec with relaxed standards, V2 spec will not import at all.
VirtualBox 5.0.22 r108108, VM Workstation 12.
It would at least be useful to know if the problem lies with VirtualBox or VMWare not being fully spec-compliant.
Same here. Created an OVF 2.0 export via "Export Appliance" in VirtualBox 4.3.0_BETA3 (Mac) and VMware Fusion 6.0.1 (Mac) could not import it:
Clicking "Retry" then gives:
Importing an OVF 1.0 export still leads to VMware complaining about it not passing the OVF spec, but then "Retry" succeeds.