Problem importing applicance
Posted: 27. May 2009, 16:01
Greetings,
I'm trying to use VirtualBox for the first time and am having problems importing an existing appliance. I've received a Fedora 10 VM that I'm trying to load into VB 2.2.2 r46594, running on an XP SP2 machine.
The first thing I tried was to import the appliance using the Import Appliance Wizard. I select the .ovf file, leave all the defaults, and let it go. The progress gets to 100%, the progress dialog closes, and the app hangs with the hour glass. If I kill the VBoxSvc process at this point, the app wakes up with an error message that the import failed. I began to dig through the VB code to see if I could find the spot that this hang is occurring at but being new to the code that didnt work out too well. Does anyone have any ideas what could be my issue?
The team that sent me the image, all using XP SP3 based machines, can import the appliance without problems. I'm thinking that some other software that I've got perhaps could be conflicting with VB, but cant figure out what. I've killed firewalls, virus scanners, etc... The other thing to note is that I do have several versions of Visual Studio on this machine. I thought maybe there would be some conflicts there, but dependencies on all of the VB binaries look fine.
Any help would be greatly appreciated.
Thanks,
Josh
I'm trying to use VirtualBox for the first time and am having problems importing an existing appliance. I've received a Fedora 10 VM that I'm trying to load into VB 2.2.2 r46594, running on an XP SP2 machine.
The first thing I tried was to import the appliance using the Import Appliance Wizard. I select the .ovf file, leave all the defaults, and let it go. The progress gets to 100%, the progress dialog closes, and the app hangs with the hour glass. If I kill the VBoxSvc process at this point, the app wakes up with an error message that the import failed. I began to dig through the VB code to see if I could find the spot that this hang is occurring at but being new to the code that didnt work out too well. Does anyone have any ideas what could be my issue?
The team that sent me the image, all using XP SP3 based machines, can import the appliance without problems. I'm thinking that some other software that I've got perhaps could be conflicting with VB, but cant figure out what. I've killed firewalls, virus scanners, etc... The other thing to note is that I do have several versions of Visual Studio on this machine. I thought maybe there would be some conflicts there, but dependencies on all of the VB binaries look fine.
Any help would be greatly appreciated.
Thanks,
Josh