VirtualBox

Ticket #11160 (new defect)

Opened 7 years ago

Last modified 3 years ago

.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:1 Changed 6 years ago by ckujau

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.

comment:2 Changed 6 years ago by frank

  • Component changed from other to OVF

comment:3 Changed 6 years ago by vw_mwa

Has anybody found a solution to this bug?

comment:4 Changed 6 years ago by Renjith

Anyone got an update about this issue?

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.

Last edited 5 years ago by dragon788 (previous) (diff)

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.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use