Problems importing appliance in Virtual Box 2.2.0 on winxp

[greekman12]

Hi,

I just installed Virtualbox 2.2.0, and decide to try the export/import feature. I exported to of my vm's to an 'appliance', and tried re-installing them. It seems to hang halfway through the process. I've tried it a couple of times, the first time I get the progress bar when It's importing, the second time no progress bar.

Both times the firt hard disk image shows up under .Virtualbox\HardDisks, but seems to get stuck there?

Anybody have this happen? Any help would be appreciated.

[greekman12]

More info on this. I tried importing an appliance with a single vm, and It seems to go well until the end when it hangs.

If I reboot, I can boot the machine, but I first have to manually re-associate the hard disk image with the machine.

[Aisling]

Hi,

what do you mean with "manually re-associate"? I've got a similar problem. Everytime when I try to import an appliance, the status bar appears and when it disappears after 100%, the mouse pointer is still in working mode and it does not disappear for hours. So I decided to close the window. Does that mean that the image has not been loaded correctly? Because when I try to start the VM, I have to restart VirtualBox and then a fatal error occurs, when starting the VM: FATAL: Could not read from the boot medium!

Perhaps your re-association could help me?!

Thanks!

[coolbiker]

I'd like to think he means taking the just imported drive and then replacing the drive he has connected to the virtual box and using the imported virtual drive.

[paullanders]

I would like to confirm this exact problem. Under VirtualBox 2.2.2 running under Windows XP I created and exported a VM appliance. When I imported into another host, the import progress bar completed, followed by an hourglass that lasted all night. After forcing VirtualBox to quit and manually killing VBoxSVC.exe I had to manually select the hard drive image for the (incompletely imported) VM. However, my imported Debian VM will not boot.

[coolbiker]

Mine will seemingly export but won't import on vista.

[wb0gaz]

I am having similar/same problem with VirtualBox 2.2.2 running on Fedora Core 10 host (i386, 32 bit.)

This is a fresh install of 2.2.2 and I'm trying to re-import a previously exported guest (XP) where there are two files (.ovf and .vmdk; the .vmdk appears to be compressed as it's about 1.1 GB while the disc image itself was 8GB.)

It is hanging with a dialog box "Importing Appliance ... (path to the .vmdk file)" and is anging at 0%.

I've tried reboot of the Fedora machine and it again reaches only this point.

[wb0gaz]

In addition to the hang problem in Import, I've also noticed that after I cancel the (incomplete) importation, the imported machine does show up in the inventory pane (left part of the main window, where VMs are listed), however, it cannot be started, settings cannot be edited, and it cannot be deleted or discarded.) Basically VirtualBox is left in a defective state. (again, this is a host on Fedora Core 10 on i386 32 bit).

[SESTH]

I'm also running into problems when importing an appliance (w2k3 guest) into an VBox 2.2.2 on w2k3 (64bit). The appliance was created with VBox 2.2.2 (64bit) on an ubuntu host. During import VBox crashes after 50% progress and the VisualStudio Debugger comes up with "An unhandled win32 exception occurred in VirtualBox.exe [4120]."