|
Reported by: |
Owned by: |
||
|
Priority: |
Component: |
||
|
Version: |
Keywords: |
||
|
Cc: |
Guest type: |
||
|
Host type: |
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.
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:
The import failed because machine.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 Fusion.
Clicking "Retry" then gives:
Line 2: Incorrect namespace 'http://schemas.dmtf.org/ovf/envelope/2' found
Importing an OVF 1.0 export still leads to VMware complaining about it not passing the OVF spec, but then "Retry" succeeds.
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