Reply to Message

I have no success so far accessing USB mass storage device from a Windows XP SP3 guest on a SUSE-11.1 ( kernel 2.6.27) host. When I connect the device ( I.e a Sandisk Cruzer USB drive) to an USB connector it is recognized by vmware and popup comes up :

The following devices can be connected to this virtual machine using the status bar Or choosing VM->Remobale devices: SanDisk Gruzer Crossfire.

If a choose to connect the drive another popup says: The specified device appears to be claimed by another deriver (usb-storage) .....

If I say OK there , nothing happens and the device never shows up in Windows. If I look now into the Windows device manager I see ,that the USB storage driver couldn't be started (Code 10).

vmware.log shows :

ec 31 11:14:48.294: vmx| USB: Found device [name:SanDisk\ Cruzer\ Crossfire vid:0781 pid:5204

path:6/2 speed:high family:storage]

Dec 31 11:14:49.482: vmx| USBG: Skipping SetConfiguration(1) due to device quirks

Dec 31 11:14:49.483: vmx| USBIO: Detect usb-storage class

Dec 31 11:14:49.529: vmx| USBGL: submit URB failed 16

Dec 31 11:14:51.471: mks| MKS lock got type None

Dec 31 11:14:54.368: vmx| USBGL: submit URB failed 16

Dec 31 11:14:56.614: mks| MKS lost grab

Dec 31 11:14:57.990: mks| MKS lost grab

Dec 31 11:14:59.389: vmx| USBGL: submit URB failed 16

Dec 31 11:15:04.395: vmx| USBGL: submit URB failed 16

Dec 31 11:15:05.086: vmx| USBG: Skipping SetConfiguration(1) due to device quirks

Dec 31 11:15:05.086: vmx| USBIO: Detect usb-storage class

Dec 31 11:15:05.095: vmx| USBGL: submit URB failed 16

Dec 31 11:15:05.750: vmx| USBG: Skipping SetConfiguration(1) due to device quirks

Dec 31 11:15:05.750: vmx| USBIO: Detect usb-storage class

Dec 31 11:15:05.757: vmx| USBGL: submit URB failed 16

Dec 31 11:15:06.472: vmx| USBG: Skipping SetConfiguration(1) due to device quirks

Dec 31 11:15:06.473: vmx| USBIO: Detect usb-storage class

Dec 31 11:15:07.158: mks| MKS switching absolute mouse off

Dec 31 11:15:07.184: mks| MKS switching absolute mouse on

Dec 31 11:15:14.763: mks| MKS lost grab

and the linux syslog shows :

Dec 31 11:14:54 PC1 kernel: usb 6-2: usbfs: process 11111 (vmware-vmx) did not claim interface 0 before use

Dec 31 11:14:59 PC1 kernel: usb 6-2: usbfs: process 11111 (vmware-vmx) did not claim interface 0 before use

Dec 31 11:15:04 PC1 kernel: usb 6-2: usbfs: process 11111 (vmware-vmx) did not claim interface 0 before use

Dec 31 11:15:04 PC1 kernel: usb 6-2: reset high speed USB device using ehci_hcd and address 5

Dec 31 11:15:04 PC1 kernel: usb 6-2: reset high speed USB device using ehci_hcd and address 5

Dec 31 11:15:05 PC1 kernel: usb 6-2: usbfs: process 11111 (vmware-vmx) did not claim interface 0 before use

Dec 31 11:15:05 PC1 kernel: usb 6-2: reset high speed USB device using ehci_hcd and address 5

Dec 31 11:15:05 PC1 kernel: usb 6-2: reset high speed USB device using ehci_hcd and address 5

Dec 31 11:15:05 PC1 kernel: usb 6-2: usbfs: process 11111 (vmware-vmx) did not claim interface 0 before use

Dec 31 11:15:05 PC1 kernel: usb 6-2: reset high speed USB device using ehci_hcd and address 5

Dec 31 11:15:06 PC1 kernel: usb 6-2: reset high speed USB device using ehci_hcd and address 5

This problem doesn't show up On SUSE-11.0 with kernel 2.6.25 but also happens on 11.0 with kernel 2.6.27