VirtualBox

Ticket #8366 (closed defect: fixed)

Opened 3 years ago

Last modified 11 months ago

Since version 4.02 I have not been able yo import and image created with go-virtual by Paragon system.

Reported by: gclarkso@… Owned by:
Priority: major Component: OVF
Version: VirtualBox 4.0.4 Keywords:
Cc: Guest type: Windows
Host type: Windows

Description (last modified by aeichner) (diff)

Result Code: VBOX_E_INVALID_OBJECT_STATE (0x80BB0007) Component: Medium Interface: IMedium {9edda847-1279-4b0a-9af7-9d66251ccc18}

When I try to import a virtual image created with G0-Virtual By Pargon software I receive this message. When I uninstall 4.0.4 and install 3.2.12 it works fine. What is the fix. The problem exists for both 4.0.4 and 4.0.2.

Change History

comment:1 in reply to: ↑ description Changed 3 years ago by phlogistonjohn

I am experiencing the same issue with an OVF file generated using ovftool (from vmware). The ovf files import fine in virtualbox 3 but fail to import in virtualbox 4. This appears to be a regression. The disk import progress bar begins but sometime before 30%, the import fails. There are three virtual disks in the OVF file. Please let me know if there is any additional information I can provide.

  Result Code: VBOX_E_INVALID_OBJECT_STATE (0x80BB0007)
  Component: Medium
  Interface: IMedium {9edda847-1279-4b0a-9af7-9d66251ccc18}

comment:2 Changed 3 years ago by teddennis

Same issue with a vmware image converted using ovftool.

comment:3 Changed 3 years ago by josuealvarez

I am experiencing the same issue (image converted with ovftool doesn't import correctly in VirtualBox 4.0.8, but it does in VirtualBox 3). I am available to further debug this issue and provide some test files if needed.

comment:4 Changed 3 years ago by poetzsch

Please attach the OVF file and note the version of the ovftool. Also all exact error messages would be helpful if they are different from the above one.

comment:5 Changed 11 months ago by aeichner

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

No response, closing. Please try with a recent release of VBox and reopen if necessary. Please attach the OVF in this case to the defect.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use