VirtualBox

Ticket #9033 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

Import failure due to OVA file name not matching the name of OVF inside OVA -> Fixed in SVN

Reported by: tdyas Owned by:
Priority: major Component: OVF
Version: VirtualBox 4.0.8 Keywords:
Cc: Guest type: other
Host type: other

Description

I exported a virtual machine to OVA format using the main VirtualBox GUI. I then renamed the OVA file before uploading it to network drive for distribution to my organization's users. When one of my users attempted to import the appliance into his VirtualBox instance, it failed to import with the following error code: (I've redacted the path name as "<pathname>.")

Failed to import appliance <pathname>

Could not read OVF file '<pathname>' (VERR_TAR_END_OF_FILE)

Details:

Result Code: VBOX_E_FILE_ERROR (0xB0BB0004) Component: Appliance Interface: IAppliance {7b148032-4124-4f46-b56a-b48ac1273f5a}

Renaming the OVA file so that it matched the name of the OVF file inside fixed the issue.

VirtualBox should either (1) not care about a mismatch between the name of the OVA and the OVF inside, or (2) display an error message that actually informs the user that they need to rename the file.

Change History

comment:1 Changed 3 years ago by michaelcole

Hi, the new OVA package is great!

This error message indicates a non-error. All kinds of things can rename a file. Users ran into this as well and it created fear/uncertainty/doubt about Virtualbox.

Seems simple enough to fix. Thanks!

comment:2 Changed 3 years ago by poetzsch

  • Summary changed from Import failure due to OVA file name not matching the name of OVF inside OVA to Import failure due to OVA file name not matching the name of OVF inside OVA -> Fixed in SVN

Fixed in SVN and the fix will be available in the next minor update.

comment:3 Changed 3 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

This is fixed in VBox 4.1.2.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use