Opened 6 years ago
Last modified 6 years ago
#17385 closed defect
OVA file made with VirtualBox 5.2.4 can't be read by VMware vCenter 6.5 — at Initial Version
| Reported by: | Bob Tanner | Owned by: | |
|---|---|---|---|
| Component: | OVF | Version: | VirtualBox 5.2.4 |
| Keywords: | VMware OVF | Cc: | |
| Guest type: | Windows | Host type: | Mac OS X |
Description
Related to https://www.virtualbox.org/ticket/7982 (which is VirtualBox 4.x defect report)
The virtualization format 0.9 no longer works!
Using Virtualbox 5.2.4 r119785 Export Appliance..., Selecting Open Virtualization Format 0.9 results in:
<vssd:VirtualSystemType>vmx-6</vssd:VirtualSystemType>
But OVF import on VMCA 6.5 throws an error, "OVF 0.9 is not supported. Invalid name space"
Using Virtualbox 5.2.4 r119785 Export Appliance..., Selecting Open Virtualization Format 1.0, create manifest file checked results in:
<vssd:VirtualSystemType>virtualbox-2.2</vssd:VirtualSystemType>
Throws error invalid OVF checksum algorithm: SHA1
Using Virtualbox 5.2.4 r119785 Export Appliance..., Selecting Open Virtualization Format 1.0, create manifest file NOT checked results in:
<vssd:VirtualSystemType>virtualbox-2.2</vssd:VirtualSystemType>
Not recognized by VMCA 6.5 on OVF import.
Using Virtualbox 5.2.4 r119785 Export Appliance..., Selecting Open Virtualization Format 2.0, create manifest file checked results in:
<vssd:VirtualSystemType>virtualbox-2.2</vssd:VirtualSystemType>
Throws error invalid OVF checksum algorithm: SHA256
Using Virtualbox 5.2.4 r119785 Export Appliance..., Selecting Open Virtualization Format 2.0, create manifest file NOT checked results in:
<vssd:VirtualSystemType>virtualbox-2.2</vssd:VirtualSystemType>
Not recognized by VMCA 6.5 on OVF import.
