#3890 closed defect (fixed)
vbox hangs when trying to import virtual appliance
| Reported by: | Frank Van Damme | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 2.2.2 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | Mac OS X |
Description
I am running virtualbox on OS X. When selecting the menu option "import appliance #I", the program stops responding and must be killed.
I don't have any more information than that, if needed please tell me how to collect more.
Change History (7)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
I suppose such dump is useful, could someone please tell me how to generate this for vbox on Mac? Thank you.
follow-up: 5 comment:3 by , 16 years ago
Replying to FrankVanDamme:
I am running virtualbox on OS X.
How long should one wait for an import of an 8GB image? I also see a 'hang' on ovf import on a 3GHz P4 desktop box where the VBox processes appear mostly idle (created on a T61 laptop, Core2 Duo, 2 GB RAM, both VBox V2.2.2 on WinXP Professional Version 2002 SP2).
Is there a way to gather further information, what would you like to see?
Regards,
Peter.
comment:4 by , 16 years ago
Same problem for me with VirtualBox 2.2.2 r46594
I created a VM under Ubuntu 9.04 (32 bits) with windows XP Pro guest and exported it without legacy OVF 0.9. I moved this VM on Windows XP Pro and import it well under the administrative account.
When I tried to import the same VM under a single user account the program hang on after 90% (I tried also under cmd with VBOXManage with same result)
Regards
Olivier Friard
follow-up: 6 comment:5 by , 16 years ago
Replying to pcc@gmx.net:
(...) I also see a 'hang' on ovf import on a 3GHz P4 desktop box where the VBox processes appear mostly idle (created on a T61 laptop, Core2 Duo, 2 GB RAM, both VBox V2.2.2 on WinXP Professional Version 2002 SP2).
I don't know how relevant this is, but I deinstalled VBox V2.2.2 and installed V2.2.0 since that was the version where the import feature initially has been introduced. Interestingly, I had an immediate failure the first time I tried:
AppName: vboxsvc.exe AppVer: 2.2.0.0 ModName: vboxsvc.exe ModVer: 2.2.0.0 Offset: 0005837c
Unfortunately, Windows did not want me to have the .dmp file that went with it, and I currently cannot reproduce this situation.
In parallel, however, I have an error which I believe has to do with remaining registry entries of the higher V2.2.2:
Código Resultado: E_INVALIDARG (0x80070057) Componente: VirtualBox Interface: IVirtualBox {779264f4-65ed-48ed-be39-518ca549e296}
This appears to be repeatable at all times and prevents any further progress.
comment:6 by , 16 years ago
Replying to pcc@gmx.net:
Replying to pcc@gmx.net:
(...) I also see a 'hang' on ovf import on a 3GHz P4 desktop box where the VBox processes appear mostly idle (created on a T61 laptop, Core2 Duo, 2 GB RAM, both VBox V2.2.2 on WinXP Professional Version 2002 SP2).
V2.2.4 seems to resolve this matter for me, thank you.
All the best,
Peter.
comment:7 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I have a similar issue. Host Mac OS X 10.5.6, MacBook Pro5,1 2.4 GHz, VB 2.2.2 r46594
Importing an appliance generated on Ubuntu host containing an Ubuntu guest. The appliance has two vmdks. During import it appears to read one vmdk. it might be reaching the end of that one and transiotioning to the next one? The progress bar hangs after about 10 minutes of progress on the first vmdk.
I can press Cancel to close the import progress dialog. But subsequently if I try to open File/Virtual Media Manager, there's no response an VB freezes and the only way to exit is to kill the process.
There are no log files generated.
Below is a thread dump generated by killing VB after tryng to open Vitual Media Manager as above:
Process: VirtualBox [625] Path: /Applications/VirtualBox.app/Contents/MacOS/VirtualBox