Import Appliance fails on WinXP 32 bit host

[Rony Shapiro]

Trying to import an appliance via VirtualBox's GUI interface, I get a non-descriptive failure message. Trying the same using VBoxManage provides a *little* more information. Fllowig is the output:

$ ./VBoxManage.exe import C:\tmp\pws-deb32.ova  --vsys 0 --unit 6 
   --ignore --vsys 0 --unit 10 --disk C:\local\VirtualBox\HardDisks\pws\pws-deb32-disk1.vmdk
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting C:\tmp\pws-deb32.ova...
OK.
Disks:  vmdisk1 8589934592      -1
        http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized   
        pws-deb32-disk1.vmdk    -1      -1

Virtual system 0:
 0: Suggested OS type: "Debian"
    (change with "--vsys 0 --ostype <type>"; use "list ostypes" to list all possible values)
 1: Suggested VM name "pws"
    (change with "--vsys 0 --vmname <name>")
 2: Number of CPUs: 1
    (change with "--vsys 0 --cpus <n>")
 3: Guest memory: 768 MB
    (change with "--vsys 0 --memory <MB>")
 4: USB controller
    (disable with "--vsys 0 --unit 4 --ignore")
 5: Network adapter: orig NAT, config 2, extra slot=0;type=NAT
 6: Floppy -- disabled
 7: CD-ROM
    (disable with "--vsys 0 --unit 7 --ignore")
 8: IDE controller, type PIIX4
    (disable with "--vsys 0 --unit 8 --ignore")
 9: IDE controller, type PIIX4
    (disable with "--vsys 0 --unit 9 --ignore")
10: Hard disk image: source image=pws-deb32-disk1.vmdk, target path=C:\local\Vir
tualBox\HardDisks\pws\pws-deb32-disk1.vmdk, controller=8;channel=0
0%...
Progress state: E_FAIL

VBoxManage.exe: error: Details: code ERROR_SUCCESS (0x0), component , interface, callee
Context: "ImportAppliance" at line 757 of file VBoxManageAppliance.cpp

Please advise. I've tried importing another appliance with the GUI (FreeBSD host), same result. This is a very nasty showstopper for me.

Thanks,

Rony

[Noel Weichbrodt]

Same bug here--non-descriptive GUI message, slightly more verbose VBoxManage error message.

Of note, the --dry-run option shows success. Only the actual import fails.

C:\Documents and Settings\noel.weichbrodt>"C:\Program Files\Oracle\VirtualBox\VB
oxManage.exe" import "E:\VirtualBox\Broadband-Dev-V3\Broadband-Dev-V3.ovf"
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting E:\VirtualBox\Broadband-Dev-V3\Broadband-Dev-V3.ovf...
OK.
Disks:  vmdisk1 34359738368     -1      http://www.vmware.com/interfaces/specifi
cations/vmdk.html#streamOptimized       Bradband-Dev-V3-disk2.vmdk      -1
-1
Virtual system 0:
 0: Suggested OS type: "Ubuntu_64"
    (change with "--vsys 0 --ostype <type>"; use "list ostypes" to list all poss
ible values)
 1: Suggested VM name "Bradband-Dev-V3"
    (change with "--vsys 0 --vmname <name>")
 2: Number of CPUs: 1
    (change with "--vsys 0 --cpus <n>")
 3: Guest memory: 1500 MB
    (change with "--vsys 0 --memory <MB>")
 4: Sound card (appliance expects "", can change on import)
    (disable with "--vsys 0 --unit 4 --ignore")
 5: USB controller
    (disable with "--vsys 0 --unit 5 --ignore")
 6: Network adapter: orig HostOnly, config 3, extra slot=0;type=HostOnly
 7: Network adapter: orig NAT, config 3, extra slot=1;type=NAT
 8: CD-ROM
    (disable with "--vsys 0 --unit 8 --ignore")
 9: IDE controller, type PIIX4
    (disable with "--vsys 0 --unit 9 --ignore")
10: IDE controller, type PIIX4
    (disable with "--vsys 0 --unit 10 --ignore")
11: SATA controller, type AHCI
    (disable with "--vsys 0 --unit 11 --ignore")
12: Hard disk image: source image=Bradband-Dev-V3-disk2.vmdk, target path=E:\Vir
tualBox\Bradband-Dev-V3\Bradband-Dev-V3-disk2.vmdk, controller=11;channel=0
    (change target path with "--vsys 0 --unit 12 --disk path";
    disable with "--vsys 0 --unit 12 --ignore")
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: E_INVALIDARG

VBoxManage.exe: error: Details: code ERROR_SUCCESS (0x0), component , interface
, callee
Context: "ImportAppliance" at line 757 of file VBoxManageAppliance.cpp

[juhajuha]

I came across with same problem. I discovered a workaround. I extracted the disk image by renaming the .ova file to .tar and then uncompressed it. I then cloned the extracted .vmdk file with "vboxmanage clonehd source.vmdk destination.vdi --format vdi" and then attached the cloned hd to a newly created virtual machine.

Perhaps this contains some unnecessary steps, but worked for me...

[Christian Pötzsch]

Having the ovf file might help in debugging this issue.

[aeichner]

No response, closing. If this is still a problem with a recent release of VirtualBox reopen the defect and attach the OVF file please.