VDI 3.2.1 Import job timeout window

Question

I am importing a Win7 desktop that will be converted to a template. The import job is timing out at about 98% done! Is there a way to increase the timeout window?

Answer 1

With encouragement and instructions from Thin Guy, i switched to importing a template and that worked fine. In fact, it was observably faster than importing a desktop, not sure why just yet.
Since it was not obvious to me how to create a template, I'll include Thin Guy's instructions here:
(1) Using the VirtualBox GUI to export an appliance will not work since it does not create the required .XML and .VDI files.
(2) The first step is to locate the .XML and .VDI files representing the VirtualBox VM you want to use for a template:
Shut down the VM. In the VirtualBox data directory (depends on platform) you'll find
<path>(.)VirtualBox(\/)Machines
That's where the xml files are. The filename will be <vm name>.xml. Move that to /var/tmp
<path>(.)VirtualBox(\/)VDI
That's where the vdi files (i.e. disk image) are. The filename(s) will be <virtual disk name>.vdi. Move that to /var/tmp
My note: if you have a .vmdk file, it can be converted to a .vdi using VBoxManage clonehd --format VDI <vmdk filename> <vdi filename>. See the man page, or just run VBoxManage and look at the Usage output.
For instance on a mac, these files are under:
/Users/$USER/Library/VirtualBox
On Solaris:
$USER/.VirtualBox
On Windows7
c:\users\username\.virtualbox
Now that the files are in /var/tmp, you need to make sure that they will be visible to VDI Manager. In my case, I am using my VDI Primary as the Virtualization Platform with no VDI sessions. This prevents me from connecting to <hostname>:1800 and doing the import. SO, I have to share out my /var/tmp and do the import from a secondary. A possible workaround is to allow sessions on the VDI Primary but I haven't tried that as yet.
Hope this helps somebody struggling as I was. Many Many Thanks to Thin Guy. He came through for me once again!