You are not logged in.

#1 2013-11-14 20:26:35

toni
Member
Registered: 2011-10-15
Posts: 437

[SOLVED] Cannot import ova file (Virtualbox)

A month ago I exported a virtual machine into ova file. Now I am trying to import it but without success.

From Virtualbox I perform the import and below error message is shown:

Failed to import appliance  /run/media/toni/DATA/Windows 7 - Development.ova.

Error reading "/run/media/toni/DATA/Windows 7 - Development.ova": element "Section" has no "type" attribute, line 18.

Result code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: Appliance
Interface: IAppliance {3059cf9e-25c7-4f0b-9fa5-3c42e441670b}

also I have tried using vboxmanage from the console:

$ vboxmanage import Windows\ 7\ -\ Development.ova 
0%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance read failed
VBoxManage: error: Error reading "/run/media/toni/DATA/Windows 7 - Development.ova": element "Section" has no "type" attribute, line 18
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Appliance, interface IAppliance
VBoxManage: error: Context: "int handleImportAppliance(HandlerArg*)" at line 304 of file VBoxManageAppliance.cpp

Could someone help me, please?

Last edited by toni (2013-11-15 00:05:25)

Offline

#2 2013-11-14 20:35:13

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: [SOLVED] Cannot import ova file (Virtualbox)

Please post all error output in English: https://wiki.archlinux.org/index.php/Fo … s_and_Code


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2013-11-15 00:05:05

toni
Member
Registered: 2011-10-15
Posts: 437

Re: [SOLVED] Cannot import ova file (Virtualbox)

jasonwryan wrote:

Please post all error output in English: https://wiki.archlinux.org/index.php/Fo … s_and_Code

Finally I have solved. But I should performed:

tar xvf myfile.ova -C /home/toni

Above command extracts three file types:

-vmdk
-ovf
-mf

Then, from virtualbox I create a new virtual machine (important: if machine exported was 32bits, new machine should be 32bits, and if exported was 64bits then new machine should be 64bits). Finally I attach the existing vmdk file instead of creating a new one and that's all. I boot up the virtual machine and it works in my case.

Anyway, I must say that despite many people say virtualbox is the best, since a lot of time ago, virtualbox always has problems when performing export/import and I think Oracle should  work hard on it to try to solve it because If not many people maybe will change to the competitor: vmware. I am a bit tired, import/export with virtualbox is really a sh....

Offline

Board footer

Powered by FluxBB