VBox 4.0.0 on Solaris 11 Express - RIM Device / Bluetooth

[guyverdh]

Neither the RIM device (Blackberry phone, via USB cable), nor the built-in bluetooh (usb device) on a Lenovo T510 pass through to Windows XP SP3 client properly.
Intermittent drops on the bluetooth, and unrecognized phone on the direct USB cable.

Any ideas or suggestions? The default Windows XP SP2 bluetooth drivers do not work for the Lenovo T510 bluetooth device.

Thanks!

[Perryg]

What version of Solaris?
Extension Pack? See Chapter 1.5. Installing VirtualBox and extension packs in your VirtualBox users guide.
How to install Extension Pack

[guyverdh]

Solaris 11 Express
VBox 4.0.0 with Extension pack installed.

With the USB Bluetooth device, it acts as though it acts like it's there, then it's gone, then back, then gone. Intermittent drop / reconnect on the device.

The communication to the USB Bluetooth device is not consistent.

With the USB attached blackberry, it must be the same way, sort of sees it, but doesn't.

[guyverdh]

So, does anyone have any clues as to why the Windows XP guest would *lose* connectivity to the pass-through USB devices momentarily, then return?

Or as to why the USB direct attached blackberry cannot be identified as such?

Is there something on the Solaris 11 Express side (also happened under Solaris 10 U8 and Solaris 10 U9 x86/x64 and previous revs of VirtualBox) that would be probing or otherwise locking the usb devices momentarily?

[guyverdh]

Okay, I've held off on re-requesting assistance on this til now due to workloads.

I've been through updates (all patches released for Solaris 11 Express snv_151a, VirtualBox 4.0.0, 4.0.2, 4.0.4, 4.0.6) none of which seem to rectify the problem.

What happens is that if I enable it in the Windows XP guest OS, and install the proper (for the laptop - Lenovo T510) bluetooth drivers, the device ready icon will go white, then after some random interval, go red (meaning the device is *gone*), then back to white after another seemingly random interval.

From the cfgadm -val command, I get

usb2/1.4 connected configured ok Mfg: Broadcom Corp Product: Broadcom Bluetooth Device NConfigs: 1 Config: 0 <no cfg str descr>

From the host os side, I see the following via prtconf -v regarding the bluetooth device.
I'll post again with the VirtualBox instance shutdown to see what native (if any) device / driver is associated with this - since this shows the vboxusb driver attached to it.

device, instance #2
Driver properties:
name='pm-components' type=string items=3 dev=none
value='NAME= vboxusb2 Power' + '0=USB D3 State' + '3=USB D0 State'
Hardware properties:
name='driver-minor' type=int items=1
value=00000000
name='driver-major' type=int items=1
value=00000002
name='configuration#' type=int items=1
value=00000001
name='usb-product-name' type=string items=1
value='Broadcom Bluetooth Device'
name='usb-vendor-name' type=string items=1
value='Broadcom Corp'
name='usb-serialno' type=string items=1
value='002713F2B4B5'
name='usb-raw-cfg-descriptors' type=byte items=216
value=09.02.d8.00.04.01.00.e0.00.09.04.00.00.03.e0.01.01.00.07.05.81.03.10.00.01.07.05.82.02.40.00.01.07.05.02.02.40.00.01.09.04.01.00.02.e0.01.01.00.07.05.83.01.00.00.01.07.05.03.01.00.00.01.09.04.01.01.02.e0.01.01.00.07.05.83.01.09.00.01.07.05.03.01.09.00.01.09.04.01.02.02.e0.01.01.00.07.05.83.01.11.00.01.07.05.03.01.11.00.01.09.04.01.03.02.e0.01.01.00.07.05.83.01.20.00.01.07.05.03.01.20.00.01.09.04.01.04.02.e0.01.01.00.07.05.83.01.40.00.01.07.05.03.01.40.00.01.09.04.01.05.02.e0.01.01.00.07.05.83.01.40.00.01.07.05.03.01.40.00.01.09.04.02.00.02.ff.ff.ff.00.07.05.84.02.20.00.01.07.05.04.02.20.00.01.09.04.03.00.00.fe.01.01.00.07.21.07.88.13.40.00
name='usb-dev-descriptor' type=byte items=18
value=12.01.00.02.e0.01.01.40.5c.0a.7f.21.60.03.01.02.03.01
name='usb-release' type=int items=1
value=00000200
name='usb-num-configs' type=int items=1
value=00000001
name='usb-revision-id' type=int items=1
value=00000360
name='usb-product-id' type=int items=1
value=0000217f
name='usb-vendor-id' type=int items=1
value=00000a5c
name='compatible' type=string items=10
value='vboxusb' + 'usba5c,217f.360' + 'usba5c,217f' + 'usba5c,classe0.1.1' + 'usba5c.classe0.1' + 'usba5c.classe0' + 'usb,classe0.1.1' + 'usb,classe0.1' + 'usb,classe0' + 'usb,device'
name='reg' type=int items=1
value=00000004
name='assigned-address' type=int items=1
value=00000005
Device Minor Nodes:
dev=(296,2)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:vboxusb
spectype=chr type=minor

[guyverdh]

Here's the prtconf -v output without VirtualBox running.

device, instance #1
Driver properties:
name='pm-components' type=string items=3 dev=none
value='NAME= usb_mid1 Power' + '0=USB D3 State' + '3=USB D0 State'
Hardware properties:
name='driver-minor' type=int items=1
value=00000000
name='driver-major' type=int items=1
value=00000002
name='configuration#' type=int items=1
value=00000001
name='usb-product-name' type=string items=1
value='Broadcom Bluetooth Device'
name='usb-vendor-name' type=string items=1
value='Broadcom Corp'
name='usb-serialno' type=string items=1
value='002713F2B4B5'
name='usb-raw-cfg-descriptors' type=byte items=216
value=09.02.d8.00.04.01.00.e0.00.09.04.00.00.03.e0.01.01.00.07.05.81.03.10.00.01.07.05.82.02.40.00.01.07.05.02.02.40.00.01.09.04.01.00.02.e0.01.01.00.07.05.83.01.00.00.01.07.05.03.01.00.00.01.09.04.01.01.02.e0.01.01.00.07.05.83.01.09.00.01.07.05.03.01.09.00.01.09.04.01.02.02.e0.01.01.00.07.05.83.01.11.00.01.07.05.03.01.11.00.01.09.04.01.03.02.e0.01.01.00.07.05.83.01.20.00.01.07.05.03.01.20.00.01.09.04.01.04.02.e0.01.01.00.07.05.83.01.40.00.01.07.05.03.01.40.00.01.09.04.01.05.02.e0.01.01.00.07.05.83.01.40.00.01.07.05.03.01.40.00.01.09.04.02.00.02.ff.ff.ff.00.07.05.84.02.20.00.01.07.05.04.02.20.00.01.09.04.03.00.00.fe.01.01.00.07.21.07.88.13.40.00
name='usb-dev-descriptor' type=byte items=18
value=12.01.00.02.e0.01.01.40.5c.0a.7f.21.60.03.01.02.03.01
name='usb-release' type=int items=1
value=00000200
name='usb-num-configs' type=int items=1
value=00000001
name='usb-revision-id' type=int items=1
value=00000360
name='usb-product-id' type=int items=1
value=0000217f
name='usb-vendor-id' type=int items=1
value=00000a5c
name='compatible' type=string items=9
value='usba5c,217f.360' + 'usba5c,217f' + 'usba5c,classe0.1.1' + 'usba5c.classe0.1' + 'usba5c.classe0' + 'usb,classe0.1.1' + 'usb,classe0.1' + 'usb,classe0' + 'usb,device'
name='reg' type=int items=1
value=00000004
name='assigned-address' type=int items=1
value=00000005
Device Minor Nodes:
dev=(230,512)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:usb_mid
spectype=chr type=minor
dev_link=/dev/usb/device1
dev=(230,513)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.devstat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/devstat
dev=(230,514)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.cntrl0
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/cntrl0
dev=(230,515)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.cntrl0stat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/cntrl0stat
dev=(230,516)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if0in1
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if0in1
dev=(230,517)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if0in1stat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if0in1stat
dev=(230,518)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if0in2
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if0in2
dev=(230,519)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if0in2stat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if0in2stat
dev=(230,520)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if0out2
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if0out2
dev=(230,521)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if0out2stat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if0out2stat
dev=(230,522)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1in3
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1in3
dev=(230,523)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1in3stat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1in3stat
dev=(230,524)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1out3
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1out3
dev=(230,525)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1out3stat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1out3stat
dev=(230,526)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.1in3
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.1in3
dev=(230,527)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.1in3stat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.1in3stat
dev=(230,528)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.1out3
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.1out3
dev=(230,529)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.1out3stat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.1out3stat
dev=(230,530)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.2in3
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.2in3
dev=(230,531)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.2in3stat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.2in3stat
dev=(230,532)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.2out3
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.2out3
dev=(230,533)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.2out3stat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.2out3stat
dev=(230,534)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.3in3
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.3in3
dev=(230,535)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.3in3stat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.3in3stat
dev=(230,536)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.3out3
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.3out3
dev=(230,537)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.3out3stat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.3out3stat
dev=(230,538)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.4in3
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.4in3
dev=(230,539)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.4in3stat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.4in3stat
dev=(230,540)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.4out3
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.4out3
dev=(230,541)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.4out3stat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.4out3stat
dev=(230,542)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.5in3
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.5in3
dev=(230,543)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.5in3stat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.5in3stat
dev=(230,544)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.5out3
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.5out3
dev=(230,545)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if1.5out3stat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if1.5out3stat
dev=(230,546)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if2in4
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if2in4
dev=(230,547)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if2in4stat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if2in4stat
dev=(230,548)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if2out4
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if2out4
dev=(230,549)
dev_path=/pci@0,0/pci17aa,2163@1a/hub@1/device@4:a5c.217f.if2out4stat
spectype=chr type=minor
dev_link=/dev/usb/a5c.217f/0/if2out4stat

[Ramshankar]

If the guest "loses" the device after it has been sucessfully seen and attached to the guest I'm afraid I can't really say what's going on much without more information. A VBox.log would be a start but in such case I might need to do extensive debugging with the device at least to see what transfers etc. it's doing.

[guyverdh]

How would I go about getting you your debug info/logs?

I can get the other logs you mentioned.

[Ramshankar]

You cannot toggle debug/flow logging without recompiling the driver yourself with the appropriate logging bits enabled. You'd have to selectively choose which logging is required. The easier option would be for me to provide you a custom debug logging driver. However, this is a bit of work and takes time to identify log locations so as to not get flooded with log data especially since this is R0 code. Therefore, prior to preparing an instrumented driver/build, I'd prefer to examine the VBox.log to see if anything is obviously wrong/misconfigured.

[guyverdh]

Updated from 4.0.0 through 4.1.6, from Solaris 11 Express through Solaris 11 11/11

Still having the same issue with usb devices seemingly randomly connecting/disconnecting.

The easiest one to show this is the bluetooth adapter.

When I try to search for new devices, it will go into scanning mode, then say that the device has disconnected or gone offline. A few seconds later, it's back online, but the scan has failed.
This will happen repeatedly.

Hardware

Lenovo T510, Model 4349-2RU

[Ramshankar]

The log file indicates nothing much, just the EHCI hub resets etc. and your device attach line itself "'00000000004c3df0[proxy 0a5c:217f]".

I don't suppose the syslog (/var/adm/messages) has any relevant info.? Could you check if it has anything related, grepping for 'vbox' in that file should be sufficient.

If nothing turns up, I'm afraid this might mean we have to debug on the device plugged in here. I don't know if we have any Bluetooth adapters in our office here, you mention "RIM" in your posts, does this also happen for a Blackberry? Maybe we might have one of those around. Not sure.

[guyverdh]

Yes, it's a Blackberry phone - older model 8830, running Blackberry OS 4.5.0

The syslog log files don't show a lot....

Nov 15 10:57:55 [hostid] mac: [ID 469746 kern.info] NOTICE: vboxvnic2 registered
Nov 15 10:57:55 [hostid] vboxdrv: [ID 891523 kern.notice] vboxusbmon: Capturing Broadcom Bluetooth Device 0xa5c:0x217f:/pci@0,0/pci17aa,2163@1a/hub@1/device
Nov 15 10:57:55 [hostid] 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
Nov 15 10:57:55 [hostid] genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,2163@1a/hub@1/device@4 (vboxusb2) online
Nov 15 10:58:54 [hostid] vboxdrv: [ID 196167 kern.notice] NOTICE: vbi_internal_alloc() failure for 2097152 bytes contig=1
Nov 15 14:10:06 [hostid] genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,2163@1a/hub@1/device@4 (vboxusb2) removed
Nov 15 14:10:16 [hostid] vboxdrv: [ID 813614 kern.notice] vboxusb: Released Broadcom Bluetooth Device 0xa5c:0x217f:864:/pci@0,0/pci17aa,2163@1a/hub@1
Nov 15 14:10:16 [hostid] genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,2163@1a/hub@1/device@4 (vboxusb2) removed
Nov 15 14:37:31 [hostid] vboxdrv: [ID 891523 kern.notice] vboxusbmon: Capturing Broadcom Bluetooth Device 0xa5c:0x217f:/pci@0,0/pci17aa,2163@1a/hub@1/device
Nov 15 14:37:31 [hostid] 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
Nov 15 14:37:31 [hostid] genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,2163@1a/hub@1/device@4 (vboxusb2) online
Nov 15 15:47:36 [hostid] vboxdrv: [ID 667893 kern.notice] vboxusbmon: Capturing USB Receiver 0x46d:0xc52b:/pci@0,0/pci17aa,2163@1a/hub@1/hub@5/device
Nov 15 15:47:36 [hostid] vboxdrv: [ID 946243 kern.notice] vboxusb: Captured USB Receiver 0x46d:0xc52b:4609:/devices/pci@0,0/pci17aa,2163@1a/hub@1/hub@5/device@6:vboxusb
Nov 15 15:47:36 [hostid] genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,2163@1a/hub@1/hub@5/device@6 (vboxusb10) online
Nov 15 15:48:23 [hostid] vboxdrv: [ID 107976 kern.notice] vboxusb: Released USB Receiver 0x46d:0xc52b:4609:/pci@0,0/pci17aa,2163@1a/hub@1/hub@5
Nov 15 15:48:23 [hostid] genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,2163@1a/hub@1/hub@5/device@6 (vboxusb10) removed
Nov 15 15:55:56 [hostid] vboxdrv: [ID 813614 kern.notice] vboxusb: Released Broadcom Bluetooth Device 0xa5c:0x217f:864:/pci@0,0/pci17aa,2163@1a/hub@1
Nov 15 15:55:56 [hostid] genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,2163@1a/hub@1/device@4 (vboxusb2) removed
Nov 15 15:55:57 [hostid] mac: [ID 736570 kern.info] NOTICE: vboxvnic2 unregistered

It doesn't appear that the Host OS is dropping the connection.

Is it possible that the Solaris hotplug service is doing something to interrupt? I have tried disabling the hotplug service to no avail.

[Ramshankar]

I see "Broadcom Bluetooth Device" as well as "USB Receiver". Does this only happen when you simultaneously use 2 USB devices to the VM? Just clarifying the situation.

[guyverdh]

There's only one bluetooth device, and while yes, it's on the usb bus, it's internal to the laptop.
Lenovo T510, Model 4349-2RU.

I've attached the DDU.submit file which shows all the devices that are part of the laptop (with the addition of the Logitech keyboard/mouse receiver M570 series trackball, K350 keyboard).

I do not attach that device (Logitech wireless adapter) to the VM as it causes the same problem in that the driver attaches / detaches making the keyboard/mouse unusable.