VirtualBox

Ticket #9414 (new defect)

Opened 3 years ago

Last modified 15 months ago

Can't import appliance because of "OVF describes no such image"

Reported by: sentin3l Owned by:
Priority: major Component: virtual disk
Version: VirtualBox 4.1.0 Keywords: OVF, image
Cc: Guest type: Linux
Host type: Linux

Description

I've created a Linux guest under Windows host (VBox 4.1.0), for configuration see MBD_Workstation.xml Download (in short: nothing special, just some snapshots). If I try to import on Linux Host I step over Bug #7941, but fail at:

00:06:28.590 Appliance::Task ERROR [COM]:
aRC=NS_ERROR_FAILURE (0x80004005) aIID={3059cf9e-25c7-4f0b-9fa5-3c42e441670b} aComponent={Appliance}
aText={<vbox:Machine> element in OVF contains a medium attachment for the disk image
f1acf25f-eb04-45ca-a5a8-d8f91be48370 but the OVF describes no such image}, preserve=false

For more Information see VBoxSVC.log Download. Any help would be greatly appreciated, I'm feeling odd about this problems at a simple Ex-/Import. If you need more details don't hesitate to ask.

Attachments

MBD_Workstation.xml Download (26.8 KB) - added by sentin3l 3 years ago.
configuration, snapshots of guest
VBoxSVC.log Download (2.0 KB) - added by sentin3l 3 years ago.
Import logfile on Linux Host
MBD_Workstation.ovf Download (16.1 KB) - added by sentin3l 3 years ago.
OVF from exported guest
MBD_Workstation_merged_snaps.ovf Download (15.8 KB) - added by sentin3l 3 years ago.
second OVF from ex- / import run for VM
VBoxSVC_merged_snaps.log Download (2.7 KB) - added by sentin3l 3 years ago.
second LOG from ex- / import run for VM
VirtualBox.xml Download (7.0 KB) - added by sentin3l 3 years ago.
vbox config from exporting win32 host
VirtualBox.2.xml Download (1.1 KB) - added by sentin3l 3 years ago.
vbox config from importing linux host

Change History

Changed 3 years ago by sentin3l

configuration, snapshots of guest

Changed 3 years ago by sentin3l

Import logfile on Linux Host

comment:1 Changed 3 years ago by poetzsch

Please add the ovf.

comment:2 Changed 3 years ago by sentin3l

Where/How can I extract the ovf? The exported file is a single 8GB ova-File and I don't see any intermediate files on target host except the extracted vmdk-Files.

comment:3 Changed 3 years ago by poetzsch

If you export the VM in the wizard change the file extensions to ".ovf" instead of ".ova". This will create the ovf with all the images separately.

comment:4 Changed 3 years ago by sentin3l

Sorry, I should read first an post then... I renamed ova to tar an extracted MBD_Workstation.ovf Download

Changed 3 years ago by sentin3l

OVF from exported guest

comment:5 Changed 3 years ago by poetzsch

I can import the ovf without problems (after I created some dummy harddisks). Also I can't find 'f1acf25f-eb04-45ca-a5a8-d8f91be48370' anywhere mentioned in the Machine config file or the ovf. So are you really sure the error message was generated from that ovf import?

comment:6 Changed 3 years ago by sentin3l

That's the point where I'm also very curios about. I'm quite familiar with xml and sort of things, but if I look for the UUID in ovf or cfg-xml I also don't find it mentioned anywhere...
I merged all snapshots and replayed the hole process of ex- and import again and got still the same error just with another (nowhere existing) UUID.

Changed 3 years ago by sentin3l

second OVF from ex- / import run for VM

Changed 3 years ago by sentin3l

second LOG from ex- / import run for VM

comment:7 Changed 3 years ago by sentin3l

Very interesting: If I extract the ova which import results in:

00:59:32.818 Appliance::Task ERROR [COM]:
aRC=NS_ERROR_FAILURE (0x80004005) aIID={3059cf9e-25c7-4f0b-9fa5-3c42e441670b} aComponent={Appliance}
aText={<vbox:Machine> element in OVF contains a medium attachment for the disk image
f4456ed5-a100-44d6-aa76-f8b6c26c5127 but the OVF describes no such image}, preserve=false

and import the ovf I get the same error, but with different (nowhere existing) UUID:

00:59:32.818 Appliance::Task ERROR [COM]:
aRC=NS_ERROR_FAILURE (0x80004005) aIID={3059cf9e-25c7-4f0b-9fa5-3c42e441670b} aComponent={Appliance}
aText={<vbox:Machine> element in OVF contains a medium attachment for the disk image
de04a919-3a68-492d-abc7-0a15791d1c2b but the OVF describes no such image}, preserve=false

Seems like a Bug, isn't?

comment:8 Changed 3 years ago by poetzsch

Yes, this is strange ofc. Unfortunately I can't reproduce that. Neither with one of my own VMs nor with your OVF. Please add your VirtualBox.xml. Maybe I see something in there.

Changed 3 years ago by sentin3l

vbox config from exporting win32 host

Changed 3 years ago by sentin3l

vbox config from importing linux host

comment:9 Changed 3 years ago by poetzsch

Still no idea. You are sure all the target disks are writeable and such? Can you manually create a VM on your Linux host?

comment:10 Changed 3 years ago by sentin3l

Hmm, this strange behavior is triggered through the existence of the invalid shared folder as described in #7941, but it still seems like a bug. Why should an invalid shared folder have such an effect on the import of images!?
I would vote for not close this bug as invalid to investigate the correlation to above mentioned shared folder bug. As for now my 'resolution' is to export without any shared folder.
Thanks for you effort poetzsch.

comment:11 Changed 3 years ago by poetzsch

Ok, I can reproduce this when I remove the shared folder part while the Import Wizard is still open. If you close the wizard before editing the file all will work. It is no good idea to change files when they are currently in use. I will think about who is to blame for it.

comment:12 Changed 3 years ago by sentin3l

Just as a sidenote - I never changed the OVF. The import wizzard do this after it found the invalid shared folder in memory. The file remains exactly the same (with invalid sf-entry).

comment:13 Changed 15 months ago by michaelloveusa

Can someone walk me through the steps to fix this? Where is you VirtualBox.xml file located? Is it in the ova?

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use