﻿id,summary,reporter,owner,description,type,status,component,version,resolution,keywords,cc,guest,host
10689,OVA Import Fails (when OVA Contains Multiple File References) => Fixed in SVN,abluesongbird,,"When I attempt to import an OVA I encounter the following error:

Failed to import appliance D:\Users\foo\Downloads\virtual-workstation-vm_OVF10.ova.

Could not open the medium storage unit 'D:\Users\foo\Downloads\system.vmdk'.

VD: error VERR_TAR_END_OF_FILE opening image file 'D:\Users\foo\Downloads\system.vmdk' (VERR_TAR_END_OF_FILE).

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: Appliance
Interface: IAppliance {3059cf9e-25c7-4f0b-9fa5-3c42e441670b}

The OVA's OVF descriptor contains two references, in this order:
1. system.vmdk and
2. sandbox.vmdk.

*The referenced files appear in the TAR archive in the same order as they do in the OVF descriptor.*

During the import, VirtualBox first loads sandbox.vmdk and then tries to load system.vmdk, resulting in the error above.

Thinking this was an alphebetization/sorting problem, I renamed the files to:
1. 00system.vmdk and
2. 01sandbox.vmdk.

This did not help.  (VirtualBox still goes for 01sandbox.vmdk first.)

Next I tried reordering the TAR archive, putting 01sandbox.vmdk before 00system.vmdk.  This time the import worked!  VirtualBox still loaded 01sandbox.vmdk first, but this time it could find 00system.vmdk.

Looking at the OVF spec, I think this is a VirtualBox bug: the spec indicates that the file order of the TAR should match the file order of the descriptor, but VirtualBox expects different orders.
",defect,closed,OVF,VirtualBox 4.1.16,fixed,,,other,other
