USB problem between Solaris11 Host & Windows7 Guest

[acf]

Unable to post detail as I appear to be breaching rules of first post ...

Detail (hopefully) to follow ...

[acf]

Dear Forum Members,

Long time Solaris user on laptop. Use Virtualbox primarily as a means to support my iPhone using iTunes.

I have been able to run this combination successfully in the past, but not for some time - since before Virtualbox pre Version 3 I suspect.

Only of late have I focused on resolving this issue in an effort to run Windows7 as a Guest VM with Solaris 11 host on my Toshiba laptop.

I have scoured various forums and usergroups over the past few days, to no avail.I have explored configs and options at Solaris, Windows7, iPhone and the VM levels, but the inability for the Windows7 guest to detect an attached iPhone remains.

I have tested iPhone against native Windows7 iTunes and it connects OK, so I expect the iPhone itself is fine. My suspicions now are with either Solaris or Virtualbox.

I am running Solaris 11 (Update 1, Build 6), Virtualbox 4.1.8 with Extension Pack, and Windows7.

I have a usbfilter set at Solaris. If I don't set the filter, Solaris can detect the iPhone, and read photo's using Gnome gtkam.

vboxuser has been added.

When I attach the iphone directly to laptop usb-port with Windows7 VM running, the VM appears to detect a device, but only loads the Apple Mobile Device Driver, with no attached iPhone. iTunes therefore detects nothing.

From VBox.log for this machine, USB Proxy errors (VERR_PIPE_IO_ERROR) are reported...

Code: Select all

VBox.Log
00:02:06.429 VUSB: attached '00000000007478f0[proxy 05ac:1294]' to port 1
00:02:06.431 EHCI: USB Operational
00:02:08.323 USBProxy:Command 0xc0185694 failed. Req.rc=VERR_PIPE_IO_ERROR
00:02:08.323 USBProxy:usbProxySolarisUrbQueue Failed!! pProxyDev=00000000007478f0[proxy 05ac:1294] pUrb=0000000001c99db0 EndPt=0x5 bEndpoint=0x85 enmType=2 enmDir=1 cbData=17920 rc=VERR_PIPE_IO_ERROR
00:02:08.344 RTC: period=0x20 (32) 1024 Hz
00:02:08.359 RTC: period=0x100 (256) 128 Hz
00:02:08.905 RTC: period=0x200 (512) 64 Hz
00:02:09.288 USBProxy:Command 0xc0185694 failed. Req.rc=VERR_PIPE_IO_ERROR
00:02:09.288 USBProxy:usbProxySolarisUrbQueue Failed!! pProxyDev=00000000007478f0[proxy 05ac:1294] pUrb=0000000001c97300 EndPt=0x1 bEndpoint=0x81 enmType=2 enmDir=1 cbData=512 rc=VERR_PIPE_IO_ERROR

In the system messages file, we see the appearance of the iPhone, though no driver available for this particular device. presumably this doesn't matter since I'll be using Windows7 and iTunes to access and manage the iPhone ...

Code: Select all

Messages extract ...
Jan 11 14:21:52 mutley usba: [ID 912658 kern.info] USB 2.0 device (usb5ac,1294) operating at hi speed (USB 2.x) on USB 2.0 external hub: device@3, usb_mid1 at bus address 3
Jan 11 14:21:52 mutley usba: [ID 349649 kern.info]      Apple Inc. iPhone dc8457cebe7f7a3dc4aad63de2de5517c7e5ea63
Jan 11 14:21:52 mutley genunix: [ID 936769 kern.info] usb_mid1 is /pci@0,0/pci1179,1@1d/hub@1/device@3
Jan 11 14:21:52 mutley genunix: [ID 408114 kern.info] /pci@0,0/pci1179,1@1d/hub@1/device@3 (usb_mid1) online
Jan 11 14:21:52 mutley usba: [ID 349649 kern.info] usba:        no driver found for interface 0 (nodename: 'image') of Apple Inc. iPhone dc8457cebe7f7a3dc4aad63de2de5517c7e5ea63

Looking at the Solaris level, we see ...

Code: Select all

Config Details :-
cfgadm -alv|grep -i phone
usb3/1.3                       connected    configured   ok         Mfg: Apple Inc.  Product: iPhone  NConfigs: 4  Config: 0  : PTP

and seen by Virtualbox ...

VBoxManage list usbhost
Host USB Devices:

UUID:               5c58dd3b-25b6-4d0a-9865-f9b5df17e21e
VendorId:           0x05ac (05AC)
ProductId:          0x1294 (1294)
Revision:           0.1 (0001)
Manufacturer:       Apple Inc.
Product:            iPhone
SerialNumber:       dc8457cebe7f7a3dc4aad63de2de5517c7e5ea63
Address:            0x5ac:0x1294:1:/pci@0,0/pci1179,1@1d/hub@1
Current State:      Busy

Any advice on how to get this working once more would be very much appreciated. Happy to submit a bug if recommended, though Solaris or VirtualBox?


Regards,

Andrew

[acf]

Brief update for forum members:-

Have identified earlier version of Solaris (snv_161) running VB 4.1.8 that can successfully interface with iPhone across a Windows guest.

Focus is now on Solaris, and some change(s) between snv_161, and the current build now named Solaris 11 Build 1 Update 7.

The system running snv_161 will be updated to latest Solaris release to ascertain whether this introduces this problem of

vboxusb:vboxUSBSolarisBulkXfer usb_pipe_bulk_xfer enmDir=0x1 Ep=0x81 failed! rc=-6

Thanks to Ram for his assistance thus far ...

Andrew

[acf]

Update.

VBox V4.1.8 r75467 on Solaris 11 (Update 1 Build 10) X86.

Following installation of a vbox usb driver for Solaris, I am now able to run Windows 7 and communicate with my iPhone via iTunes.

I still have intermittent problems, largley concerning USB 3 support on Solaris (I think), but as far as this particular thread is concerned, I now have a working configuration!

Many thanks to Ram for his help and supply of new driver.

I shall pursue other issues separately to this.

Andrew

[Guyver]

Wonder if the new driver would fix my usb issues...

[Ramshankar]

Wonder if the new driver would fix my usb issues...

Which host (uname -a, /etc/release pkg info kernel output) are you on? (Sorry if I asked this before)

[Guyver]

SunOS 5.11 11.0 i86pc i386 i86pc
Oracle Solaris 11 11/11 X86

Description: Core operating system kernel, device drivers and other modules.
FMRI: pkg://solaris/system/kernel@0.5.11,5.11-0.175.0.4.0.5.1:20120206T230052Z
Name: system/kernel/cpu-counters
FMRI: pkg://solaris/system/kernel/cpu-counters@0.5.11,5.11-0.175.0.0.0.2.1:20111019T073913Z
Name: system/kernel/dynamic-reconfiguration/i86pc
FMRI: pkg://solaris/system/kernel/dynamic-reconfiguration/i86pc@0.5.11,5.11-0.175.0.0.0.2.1:20111019T073930Z
Name: system/kernel/i86pc/fipe
FMRI: pkg://solaris/system/kernel/i86pc/fipe@0.5.11,5.11-0.175.0.0.0.2.1:20111019T074018Z
Name: system/kernel/i86pc/ioat
FMRI: pkg://solaris/system/kernel/i86pc/ioat@0.5.11,5.11-0.175.0.0.0.2.1:20111019T074029Z
Name: system/kernel/platform
Description: core kernel software for a specific hardware platform group
FMRI: pkg://solaris/system/kernel/platform@0.5.11,5.11-0.175.0.4.0.5.1:20120206T225947Z
Name: system/kernel/power
FMRI: pkg://solaris/system/kernel/power@0.5.11,5.11-0.175.0.0.0.2.1:20111019T074742Z
Name: system/kernel/secure-rpc
Summary: kernel RPCSEC_GSS
Description: kernel GSS-API services for ONC RPC
FMRI: pkg://solaris/system/kernel/secure-rpc@0.5.11,5.11-0.175.0.0.0.2.1:20111019T074754Z
Name: system/kernel/security/gss
Summary: kernel GSSAPI V2
2 - kernel
FMRI: pkg://solaris/system/kernel/security/gss@0.5.11,5.11-0.175.0.0.0.2.1:20111019T074809Z
Name: system/kernel/suspend-resume
FMRI: pkg://solaris/system/kernel/suspend-resume@0.5.11,5.11-0.175.0.0.0.2.1:20111019T074824Z

[Ramshankar]

Okay that looks compatible, I'll try upload the S11 175 built driver on Monday.

[Guyver]

Great! Looking forward to it

[Ramshankar]

Actually, I'm busy today with some other issue requiring me to use snv_166, so I dug out the driver I gave acf from my e-mail archive. Uploading it here, hope it works.

Here's the instructions on how to install it:

Code: Select all

1. stop all VMs
2. rem_drv vboxusb (you shouldn't get any errors in this command)
3. Copy vboxusb from the zip file to /platform/i86pc/kernel/drv/amd64/ (backup old vboxusb if you want to)
4. add_drv vboxusb (you'll get a failed to attach error which is normal)

Check that the new vboxusb is loaded using "modinfo | grep vbox", the vboxusb version alone would be something new (not 4.1.8 as the rest of the modules). If this is so, then the new driver is active. Feel free to ask if I didn't make anything clear or you run into some issues.

[Guyver]

Definitely seeing more information in the dmesg (syslog) output when capturing/releasing usb devices.

Unfortunately it didn't help with the device appearing/disappearing flip/flop inside the VM.

Attempting full restart just for grins.

Restart didn't seem to help.

Here's an extract from the /var/adm/messages file - the extract is what showed up after I clicked on the usb device inside of virtualbox to take it over (the usb device being the Broadcomm bluetooth adapter).

Mar 5 13:17:55 nurb5054739 genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,2163@1a/hub@1/device@4 (usb_mid1) removed
Mar 5 13:17:55 nurb5054739 vboxdrv: [ID 891523 kern.notice] vboxusbmon: Capturing Broadcom Bluetooth Device 0xa5c:0x217f:/pci@0,0/pci17aa,2163@1a/hub@1/device
Mar 5 13:17:55 nurb5054739 vga_arbiter: [ID 197929 kern.info] vga_arbiter: device added: PCI:0:1:0.0,decodes=io+mem+IO+MEM,owns=io+mem+IO+MEM,legalocks=none,normlocks=none
Mar 5 13:17:55 nurb5054739 vga_arbiter: [ID 254375 kern.info] 1 vga device(s) found
Mar 5 13:17:55 nurb5054739 rootnex: [ID 349649 kern.info] vga_arbiter0 at root
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] vga_arbiter0 is /vga_arbiter
Mar 5 13:17:55 nurb5054739 vboxdrv: [ID 632280 kern.notice] vboxusb: Captured Broadcom Bluetooth Device 0xa5c:0x217f:864:/devices/pci@0,0/pci17aa,2163@1a/hub@1/device@4:vboxusb
Mar 5 13:17:55 nurb5054739 genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,2163@1a/hub@1/device@4 (vboxusb2) online
Mar 5 13:17:55 nurb5054739 pseudo: [ID 129642 kern.info] pseudo-device: fct0
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] fct0 is /pseudo/fct@0
Mar 5 13:17:55 nurb5054739 pseudo: [ID 129642 kern.info] pseudo-device: stmf0
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] stmf0 is /pseudo/stmf@0
Mar 5 13:17:55 nurb5054739 pseudo: [ID 129642 kern.info] pseudo-device: llc10
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1@0
Mar 5 13:17:55 nurb5054739 pseudo: [ID 129642 kern.info] pseudo-device: lofi0
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi@0
Mar 5 13:17:55 nurb5054739 pseudo: [ID 129642 kern.info] pseudo-device: ramdisk1024
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] ramdisk1024 is /pseudo/ramdisk@1024
Mar 5 13:17:55 nurb5054739 pseudo: [ID 129642 kern.info] pseudo-device: ucode0
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] ucode0 is /pseudo/ucode@0
Mar 5 13:17:55 nurb5054739 pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm@0
Mar 5 13:17:55 nurb5054739 pseudo: [ID 129642 kern.info] pseudo-device: fcp0
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp@0
Mar 5 13:17:55 nurb5054739 pseudo: [ID 129642 kern.info] pseudo-device: sdt0
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt@0
Mar 5 13:17:55 nurb5054739 pseudo: [ID 129642 kern.info] pseudo-device: fbt0
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt@0
Mar 5 13:17:55 nurb5054739 pseudo: [ID 129642 kern.info] pseudo-device: dcpc0
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] dcpc0 is /pseudo/dcpc@0
Mar 5 13:17:55 nurb5054739 pseudo: [ID 129642 kern.info] pseudo-device: profile0
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] profile0 is /pseudo/profile@0
Mar 5 13:17:55 nurb5054739 pseudo: [ID 129642 kern.info] pseudo-device: lockstat0
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat@0
Mar 5 13:17:55 nurb5054739 pseudo: [ID 129642 kern.info] pseudo-device: systrace0
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace@0
Mar 5 13:17:55 nurb5054739 tpm: [ID 568822 kern.info] NOTICE: TPM found: Ver 1.2, Rev 8.16, SpecLevel 2, errataRev 2, VendorId 'STM '
Mar 5 13:17:55 nurb5054739 pseudo: [ID 129642 kern.info] pseudo-device: bpf0
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] bpf0 is /pseudo/bpf@0
Mar 5 13:17:55 nurb5054739 pseudo: [ID 129642 kern.info] pseudo-device: winlock0
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] winlock0 is /pseudo/winlock@0
Mar 5 13:17:55 nurb5054739 pseudo: [ID 129642 kern.info] pseudo-device: nsmb0
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] nsmb0 is /pseudo/nsmb@0
Mar 5 13:17:55 nurb5054739 pseudo: [ID 129642 kern.info] pseudo-device: fssnap0
Mar 5 13:17:55 nurb5054739 genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap@0
Mar 5 13:17:57 nurb5054739 vboxdrv: [ID 854772 kern.notice] vboxusb:vboxUSBSolarisBulkXfer usb_pipe_bulk_xfer enmDir=0x1 Ep=0x82 failed! rc=-6
Mar 5 13:21:09 nurb5054739 last message repeated 17 times
Mar 5 13:21:20 nurb5054739 vboxdrv: [ID 854772 kern.notice] vboxusb:vboxUSBSolarisBulkXfer usb_pipe_bulk_xfer enmDir=0x1 Ep=0x82 failed! rc=-6


Note the usb_pipe_bulk_xfer message... not sure if it's a problem or not, but it's the first time I recall seeing it.

[Ramshankar]

Too bad, I'll take a look.

[Guyver]

It was worth a shot, and it appears I'm getting more *activity* from the messages file which is a step up from what I was getting.
Why did it change my date of joining to Feb 2012 rather than keep my old name/join date???

[Guyver]

Did a complete fresh re-load of Solaris 11 11/11 last night, patched to current, loaded VBox 4.1.12, installed extensions (gave error 255 when installing / uninstalling using escallated privelege, but showed that they were installed)

Started the XP instance, re-enabled the bluetooth usb device, re-loaded the bluetooth driver stack - all to no avail. Still the device flip-flops between online/offline.

[meyerde]

Very close to the same issue... Though this time with a Android based phone...

VB 4.1.12 r77245
All packs/extensions installed

This is on 5.10 Generic 139556-08 i86pc i386 i386pc I know it is older but seeing that someone just loaded 11 with all the up to date patches and it doesnt work

Seeing the date of the thread I thought ok.. maybe this has not made it into the new release so I will try it.. What I found was weird

rem_drv vboxusb (Not installed) -- Ok.. well lets install it
Followed the rest of the instructions - Said it installed
modinfo | grep vbox

I had nothing that said usb in it just

vboxnet, vboxdrv,vboxflt,vboxflt (yes two vboxflt)

If I try the add_drv vboxusb again it says it is already installed... Just for giggles I did a touch /reconfigure and rebooted nothing changed...

Any suggestions?