VirtualBox

Ticket #6306 (closed defect: fixed)

Opened 4 years ago

Last modified 11 months ago

Export/Import Appliance not working

Reported by: dmarescajr Owned by:
Priority: major Component: OVF
Version: VirtualBox 3.1.4 Keywords:
Cc: Guest type: Windows
Host type: Windows

Description (last modified by aeichner) (diff)

VM Config file:  http://pastebin.com/cHtiFK49

Exporting a VM to .ovf works fine and dandy, but when trying to Import, it get's to the end and fails with MANIFEST_MISMATCH or something.

Error log ==v Result Code: VBOX_E_FILE_ERROR (0x80BB0004) Component: Appliance Interface: IAppliance {e3ba9ab9-ac2c-4266-8bd2-91c4bf721ceb}

Tried this many ways, even exporting/importing to local hd. Bug?

Attachments

{9bd33082-72f1-4ccc-9b4a-9024b95c4cc0}.head Download (97.7 KB) - added by vladimir.dyuzhev 4 years ago.
Head 100K of exported disk that cannot be imported.
CannotImport.PNG Download (20.7 KB) - added by vladimir.dyuzhev 4 years ago.
To get exact error code, I tried to open the disk in Media Manager (import takes much longer time to fail)
OriginalDiskHeader.head Download (97.7 KB) - added by vladimir.dyuzhev 4 years ago.
Attached the header of the disk before export -- to compare with the exported copy.

Change History

comment:1 Changed 4 years ago by vladimir.dyuzhev

Almost the same here, except error is VERR_NOT_SUPPORTED (or something like that).

I do export of the applicance, backup the whole Virtual Box directory then delete it, start VirtualBox (it creates directory from scratch), and try to import the just exported appliance. And it fails. Same machine, same everything.

I'm going to attach first 100K of the failed *.vmdk -- I suspect the error is in the header. I can provide original and converted disk too, but it's about 1G in size.

Changed 4 years ago by vladimir.dyuzhev

Head 100K of exported disk that cannot be imported.

Changed 4 years ago by vladimir.dyuzhev

To get exact error code, I tried to open the disk in Media Manager (import takes much longer time to fail)

comment:2 Changed 4 years ago by vladimir.dyuzhev

P.S. build 3.1.4r57640

Changed 4 years ago by vladimir.dyuzhev

Attached the header of the disk before export -- to compare with the exported copy.

comment:3 Changed 4 years ago by umoeller

If you get a manifest mismatch, then probably one of the files exported has changed so the checksums in the manifest (.mf) file do not match the actual file any more. As a workaround, delete the .mf file, then VirtualBox skips those checks on import.

Other than that, can you try exporting and importing again with 3.2.6 which will probably come out today? If you still get manifest errors, then there seems to be a bug in our code and we would need all the files in question to figure out what exactly is going on. Thank you!

comment:4 Changed 4 years ago by vladimir.dyuzhev

For manifest mismatch you comment might be true. Not so for my case (described in the case later). Export with immediate import doesn't work. Still doesn't work with the VB version downloaded 1 week ago.

comment:5 Changed 11 months ago by aeichner

  • Status changed from new to closed
  • Resolution set to fixed
  • Description modified (diff)

Please try again with a recent release of VBox. The problem could be fixed in the meantime. Closing for now, please reopen if necessary.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use