Unable to import a previously exported guest

[wb0gaz]

In VirtualBox 2.2.0 on Fedora Core 10 (i386 32 bit) I created a new guest system (XP) and then exported it (creating a .vmdk and .ovf file.) I stored these two files on a DVD disc.

I then fully removed VirtualBox 2.2.0 (rpm --erase) including removing $HOME/.VirtualBox, any sub-directories, and the existing disc image file.

I then did a fresh install of VirtualBox 2.2.0 (rpm --install), and started File->Import.

The dialog box "Importing Appliance ... : import appliance (path to the files on my DVD)... (2/2" hangs at 0%.

There is no activity on the DVD disc.

I had posted this same message as a follow-up over in the windows-host area, but realized this should be posted here.

Thanks,

Dave

[tzd]

I'm having the same problem with a fresh install of Ubuntu Jaunty, bare minimum system with SSH basically. This Ubuntu machine serves as the physical host for a few other ubuntu jaunty servers that I'd like to import. It's all headless and when issuing the VBoxManage import ... ovr command it starts counting up... all the way up to 90% and then it stops. It just stays there until I close it with ctrl+c.

Furthermore, when I open up a new terminal and try to import a different server (this is during the same session) it shows me a different message;

"Interpreting server2.ovf..."

In the end I have to reboot to start importing again, just to be met with the 90% stop. I've tried with a few different settings (enable PAE etc.) and deleted the .VirtualBox folder under my home-dir. None of this helped though.

I'm using v. 2.2.2 of VBox.

[Perryg]

My results of export and import.
I did the export and import via the VBox GUI. Testing was on Vista business 32bit Host -- VBox 2.2.2 PUEL -- 32bit guest OS.

• Exported to file in separate folder then burned to DVD the (2) files that were needed.
  I then imported the system to the same (Vista Host) and it imported and worked.
  I then imported the same system via DVD to my laptop running Ubuntu Jaunty and it worked as well.
  A few settings that were not show stoppers were not transferred and they were the Video memory, USB, and Shared Folders. These must be set manually.

There are a few things that may impact your ability of doing the above including the actual burning of the DVD. Sometimes there are compatibility issues of the DVD between different systems. Burning at a slower speed most of the time will correct this.

Other problems can be with the actual export function. You can actually test the export function while it is on the Host to determine if it actually exported properly.

• From terminal run VBoxManage import <name of export>.ovf --dry-run
  This will show you the settings that were exported and give you an idea of problems that may cause it to not work in the system you are importing to. 8.6. VBoxManage import of the VB Users guide will give you information of what and how to change, mix. or match settings.

[craig100]

I think I'm suffering from a similar problem. VB 2.2.2 is installed on my workstation running Ubuntu 9.04. I built an XP Pro Dev Environment on it and exported it using the VB Gui (I'm ex Windows so don't like command lines!). I then installed VB on my Sony laptop and copied the ovf and vmdk to my home directory. When trying to import the appliance I get "Cannot register the hard disk xxxxx.vmdk with UUID yyyyyy because it already exists". If I try to create a new VM and use the existing hard drive vmdk then it appears to work until I try to boot, when it cycles between the Windows XP startup screen and the SUN VB start up screen ad infinitum.

Any advice appreciated.

Craig

[Perryg]

What the information is trying to tell you is that for what ever reason the UUID of the import is exactly like one you already have on the laptop. You can verify this by looking at the VirtualBox.xml file and comparing the UUID numbers. You can read the section I indicated above to see how to change the parms of the import so they do not collide.
Conversely you can do the import --dry-run to see what the parms are for the one you are trying to install in the newly created VM. The important values must match or you will get exactly what you are describing.

[craig100]

Success! Edited the VirtualBox.xml file by removing the two <HardDisk /> child nodes of the <HardDisk /> node and then doing a normal import. Everything has started up fine this time.

Craig

[craig100]

Success! Edited the VirtualBox.xml file by removing the two <HardDisk /> child nodes of the <HardDisk /> node and then doing a normal import. Everything has started up fine this time.

Craig

Correction above, should have been "removing the two <HardDisk /> child nodes of the <HardDisks /> node" of course.

Craig

[Lord_ZealoN]

The problem we are having is:

Exporting a WinXP guest from an OpenSuse 11.1 64bits with compatibility OVF.

It imports in the same machine without troubles.

Trying to import in other machine, with OpenSuse 11.1 32bits host, once the import vmdk finishes, VirtualBox freeze. The VM is created, but without any disk associated. If I try to link to the original VMDK, the machine throw a marvelous blue screen at boottime, and reboot the guest OS.

Some idea?

[Perryg]

While you can import a 32 but OS into a 64 bit system I have my doubts that you can do this in reverse unless the PC is a full 64bit unit with the Hyper-v turned on in the bios.

[Lord_ZealoN]

I forgot to mention.

WinXP guest, is 32bits

[regli]

I am struggling with very similar issues. I also got the hangs but editing the xml file fixed that.

However, now that it started importing, at the end I get a "failed to import appliance".

Export system is Vista x64. Import system is Windows 7 x64. There should not be an issue with this at all. I am baffled how little tested this process appears to be. My scneario is as simple as it comes.

I guess I need to go and look at the command line to get an real idea what is happening. I love VB but this basic a function should simply work when it is released.

Addendum:

To overcome the problem I simply cloned the VMDK to a VDI data store:

VBoxManage -nologo clonehd source.vmdk destination.vdi -format VDI

and then created a new virtual machine with the VDI data store as the primary hard disk.