Can't attach USB Device: Apple iPod => fixed in SVN

This is a known issue and has already been fixed internally, unfortunately the fix came a few minutes after 3.1.2 was released. Hence the fix for making the iPod work will be part of the subsequent release.

Thanks for reporting though.

Replying to ramshankar:

This is a known issue and has already been fixed internally, unfortunately the fix came a few minutes after 3.1.2 was released. Hence the fix for making the iPod work will be part of the subsequent release. Thanks for reporting though.

thanks to you too, hope to get the next relase asap (or there are some "internal" build to try?)

Uploaded a test build for you here: http://www.virtualbox.org/download/testcase/VirtualBox-3.1.3-SunOS-r56280.tar.gz

The link expires in 14 days. Just to be sure you're testing the new version, check the output of "modinfo | grep vb". Thank you for your feedback.

Replying to ramshankar:

Uploaded a test build for you here: http://www.virtualbox.org/download/testcase/VirtualBox-3.1.3-SunOS-r56280.tar.gz The link expires in 14 days. Just to be sure you're testing the new version, check the output of "modinfo | grep vb". Thank you for your feedback.

installed:

$ modinfo | grep vb
190 fffffffff7e087f0    a88 288   1  vboxnet (VirtualBox NetAdp 3.1.3r56280)
192 fffffffff7d23000  24de8 287   1  vboxdrv (VirtualBox HostDrv 3.1.3r56280)
239 fffffffff7ffab00   6a20 289   1  vboxflt (VirtualBox NetDrv 3.1.3r56280)
239 fffffffff7ffab00   6a20   -   1  vboxflt (VirtualBox NetMod 3.1.3r56280)
240 fffffffff8001150   4598 290   1  vboxusbmon (VirtualBox USBMon 3.1.3r56280)
241 fffffffff8903000   6e98 292   1  vboxusb (VirtualBox USB 3.1.3r56280)

but no effect:

list usbhost reports this:

UUID:               d37a1c74-b3bb-4ffa-9773-77a9eb5b494f
VendorId:           0x05ac (05AC)
ProductId:          0x1262 (1262)
Revision:           0.1 (0001)
Manufacturer:       Apple Inc.
Product:            iPod
SerialNumber:       000A27001B670D71
Address:            0x5ac:0x1262:1:/pci@0,0/pci1179,1@1a,7
Current State:      Busy

if I attach it:

$ VBoxManage controlvm "WinXP Test" usbattach d37a1c74-b3bb-4ffa-9773-77a9eb5b494f
VirtualBox Command Line Management Interface Version 3.1.3
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

the state changes to "Captured" but I don't have any device under windows, and the menu Devices->USB Devices the iPod is not flagged; same effect if I try to flag it with the menu.

With your iPod plugged in, setup a USB filter for the VM. Then unplug your iPod, start your VM and replug it in a few seconds later.

Solaris does not let go of the iPod and is rather a shortcoming of the Solaris USBA/device detachment subsystem than VBox's fault, certain devices like the iPod need USB filters.

Replying to ramshankar:

With your iPod plugged in, setup a USB filter for the VM. Then unplug your iPod, start your VM and replug it in a few seconds later.

thanks, now all work fine, I just sync my iPod! great!!!!

I seem to have a very similar problem as described in this ticket while attaching a Nexus One to my Windows guest under OpenSolaris?. I'm running VirtualBox 3.1.4 r57640 under svn_133.

I can sometimes get it to work with the following steps, although only sometimes will it work:

1) Close down vbox 2) modunload vboxusb and vboxusbmon 3) start vboxmanager, create the filter 4) detach device 5) start vbox guest instance 6) attach device

SOMETIMES (maybe 10% of the time), vbox is able to beat usba in the race to capture the device. If and when I do get it to attach, if I need to disconnect the device while running vbox, it will fail to recapture it, and on subsequent launches of vbox it will not capture it.

Unloading the modules again in some cases has worked, but usually the "Current State" from list usbhost goes from "Held" to "Busy", possibly stopping at "Captured" briefly, although it won't actually attach under vbox and will go back to "Busy".

I can open a new case if necessary, however this seems to be the same or similar behavior as was intended to be fixed by this ticket's resolution.

Thanks!

Please consider opening a separate defect, and "2) modunload vboxusb and vboxusbmon" is not something you should ever have to do and in your list of steps you don't mention where you re-load these modules.

Could you please open a new defect with the details? Thank you.

Ok I'll open another one. The modules are loaded by VBoxManage and by the gui. There is no need to manually load them.

Please check if your fixes are not related to regression in ticket #6251 http://www.virtualbox.org/ticket/6251

Thanks