Solaris 11.1 VirtualBox USB issues with client Win7

Discussions related to using VirtualBox on Solaris hosts.
alland
Posts: 2
Joined: 30. Mar 2011, 10:36
Primary OS: OpenSolaris 11
VBox Version: OSE other
Guest OSses: Windows XP

Solaris 11.1 VirtualBox USB issues with client Win7

Post by alland »

I am using Solaris 11.1 (SunOS 5.11 11.1 i86pc i386 i86pc Solaris) as my host and Win 7 as my client. I’ m using VirtualBox version 4.2.12 r84980. My USB printer and thumb drives work okay with the Solaris host by not with my client, Win7.

This is the error code I get using my USB thumb drive:

vboxdrv: [ID 351244 kern.notice] vboxusb:vboxUSBSolarisBulkXfer usb_pipe_bulk_xfer enmDir=0x2 Ep=0x1 failed! rc=-6

Looking at Win 7 device manager, this is the error code:
USB Mass Storage Device-- This device cannot start. (Code 10)

Same error code with my USB printer:

vboxdrv: [ID 861514 kern.notice] vboxusb:vboxUSBSolarisBulkXfer usb_pipe_bulk_xfer enmDir=0x2 Ep=0x2 failed! rc=-6

Looking at Win 7 device manager, this is the error code:
Epson Mass Storage Device-- This device cannot start. (Code 10)

Same error with my USB Parallax development board:

vboxdrv: [ID 861514 kern.notice] vboxusb:vboxUSBSolarisBulkXfer usb_pipe_bulk_xfer enmDir=0x2 Ep=0x2 failed! rc=-6
noteirak
Site Moderator
Posts: 5229
Joined: 13. Jan 2012, 11:14
Primary OS: Debian other
VBox Version: OSE Debian
Guest OSses: Debian, Win 2k8, Win 7
Contact:

Re: Solaris 11.1 VirtualBox USB issues with client Win7

Post by noteirak »

Please read Minimum information needed for assistance and provide the VM log file and the guest config output.
Hyperbox - Virtual Infrastructure Manager - https://apps.kamax.lu/hyperbox/
Manage your VirtualBox infrastructure the free way!
Guyver
Posts: 104
Joined: 11. Feb 2012, 06:19
Primary OS: Solaris
VBox Version: PUEL
Guest OSses: Windows 7
Location: Central United States

Re: Solaris 11.1 VirtualBox USB issues with client Win7

Post by Guyver »

This problem has been reported repeatedly by multiple users of VIrtualBox on Solaris 11 (express to current) - consistently having issues with usb devices.

I personally have several open items.

The info I have (per your link)..

Code: Select all

VBoxManage list --long vms
Name:            uswdmclpb72ad2v
Groups:          /
Guest OS:        Windows 7 (64 bit)
UUID:            46a482da-86d5-4f85-8e9f-cc39c947c737
Config file:     /VMs/uswdmclpb72ad2v/uswdmclpb72ad2v.vbox
Snapshot folder: /VMs/uswdmclpb72ad2v/Snapshots
Log folder:      /VMs/uswdmclpb72ad2v/Logs
Hardware UUID:   46a482da-86d5-4f85-8e9f-cc39c947c737
Memory size:     4096MB
Page Fusion:     off
VRAM size:       256MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  2
Synthetic Cpu:   off
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): DVD
Boot Device (2): HardDisk
Boot Device (3): Not Assigned
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          on
PAE:             on
Time offset:     0ms
RTC:             local time
Hardw. virt.ext: on
Hardw. virt.ext exclusive: on
Nested Paging:   on
Large Pages:     on
VT-x VPID:       on
State:           running (since 2013-06-04T13:53:05.485000000)
Monitor count:   1
3D Acceleration: on
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address: 
Teleporter Password: 
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration: 
Autostart Enabled: off
Autostart Delay: 0
Storage Controller Name (0):            IDE
Storage Controller Type (0):            ICH6
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
Storage Controller Name (1):            SAS
Storage Controller Type (1):            unknown
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  8
Storage Controller Port Count (1):      8
Storage Controller Bootable (1):        on
IDE (1, 0): Empty
SAS (0, 0): /VMs/uswdmclpb72ad2v/uswdmclpb72ad2v.vdi (UUID: 3c55777a-3bfd-4310-b99e-1aa2e3fdbc10)
NIC 1:           MAC: 080027A3ABCE, Attachment: Bridged Interface 'net0 - Ethernet', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: allow-vms, Bandwidth group: none
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
Pointing Device: PS/2 Mouse
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: SolAudio, Controller: HDA)
Clipboard Mode:  Bidirectional
Drag'n'drop Mode:  disabled
VRDE:            disabled
USB:             enabled
EHCI:            enabled

USB Device Filters:

<none>

Bandwidth groups:  <none>

Shared folders:  

Guest:

Configured memory balloon size:      0 MB


----------------------------------------------------------------------
 VBoxManage list --long extpacks
Extension Packs: 1
Pack no. 0:   Oracle VM VirtualBox Extension Pack
Version:      4.2.12
Revision:     84980
Edition:      
Description:  USB 2.0 Host Controller, VirtualBox RDP, PXE ROM with E1000 support.
VRDE Module:  VBoxVRDP
Usable:       true 
Why unusable: 
-----------------------------------------------------------------------------
$ VBoxManage showvminfo uswdmclpb72ad2v                                                             
Name:            uswdmclpb72ad2v
Groups:          /
Guest OS:        Windows 7 (64 bit)
UUID:            46a482da-86d5-4f85-8e9f-cc39c947c737
Config file:     /VMs/uswdmclpb72ad2v/uswdmclpb72ad2v.vbox
Snapshot folder: /VMs/uswdmclpb72ad2v/Snapshots
Log folder:      /VMs/uswdmclpb72ad2v/Logs
Hardware UUID:   46a482da-86d5-4f85-8e9f-cc39c947c737
Memory size:     4096MB
Page Fusion:     off
VRAM size:       256MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  2
Synthetic Cpu:   off
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): DVD
Boot Device (2): HardDisk
Boot Device (3): Not Assigned
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          on
PAE:             on
Time offset:     0ms
RTC:             local time
Hardw. virt.ext: on
Hardw. virt.ext exclusive: on
Nested Paging:   on
Large Pages:     on
VT-x VPID:       on
State:           running (since 2013-06-04T13:53:05.485000000)
Monitor count:   1
3D Acceleration: on
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address: 
Teleporter Password: 
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration: 
Autostart Enabled: off
Autostart Delay: 0
Storage Controller Name (0):            IDE
Storage Controller Type (0):            ICH6
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
Storage Controller Name (1):            SAS
Storage Controller Type (1):            unknown
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  8
Storage Controller Port Count (1):      8
Storage Controller Bootable (1):        on
IDE (1, 0): Empty
SAS (0, 0): /VMs/uswdmclpb72ad2v/uswdmclpb72ad2v.vdi (UUID: 3c55777a-3bfd-4310-b99e-1aa2e3fdbc10)
NIC 1:           MAC: 080027A3ABCE, Attachment: Bridged Interface 'net0 - Ethernet', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: allow-vms, Bandwidth group: none
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
Pointing Device: PS/2 Mouse
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: SolAudio, Controller: HDA)
Clipboard Mode:  Bidirectional
Drag'n'drop Mode:  disabled
Video mode:      1600x900x32
VRDE:            disabled
USB:             enabled
EHCI:            enabled

USB Device Filters:

<none>

Available remote USB devices:

<none>

Currently Attached USB Devices:

<none>

Bandwidth groups:  <none>

Shared folders:  

VRDE Connection:    not active
Clients so far:     0

Guest:

Configured memory balloon size:      0 MB
OS type:                             Windows7_64
Additions run level:                 3
Additions version:                   4.2.12 r84980


Guest Facilities:

Facility "VirtualBox Base Driver": active/running (last update: 2013/06/04 13:54:01 UTC)
Facility "VirtualBox System Service": active/running (last update: 2013/06/04 13:55:02 UTC)
Facility "VirtualBox Desktop Integration": active/running (last update: 2013/06/04 13:56:28 UTC)
Facility "Seamless Mode": active/running (last update: 2013/06/04 13:54:01 UTC)
Facility "Graphics Mode": active/running (last update: 2013/06/04 13:54:01 UTC)
-----------------------------------------------------------------------------

Any time I try to use a USB device, I get the bulk xfer errors in my vbox log file.
The usb device will appear, then disappear - flip flopping there / not there - every few seconds.

You can see previous postings for additional information.
Last edited by noteirak on 4. Jun 2013, 18:02, edited 1 time in total.
Reason: Added code markup
bqbauer
Posts: 159
Joined: 14. Dec 2008, 22:04

Re: Solaris 11.1 VirtualBox USB issues with client Win7

Post by bqbauer »

This is a known bug of 4.1 & 4.2. I created bug ticket 11747, and it doesn't appear to have received any attention yet. Please contribute to the bug ticket to help us all have this resolved:

https://www.virtualbox.org/ticket/11747
Guyver
Posts: 104
Joined: 11. Feb 2012, 06:19
Primary OS: Solaris
VBox Version: PUEL
Guest OSses: Windows 7
Location: Central United States

Re: Solaris 11.1 VirtualBox USB issues with client Win7

Post by Guyver »

I first reported this issue back when I was running under Solaris 11 express, January 2011... It's been over 2 and a half years without a fix.

viewtopic.php?f=11&t=37858
Ramshankar
Oracle Corporation
Posts: 793
Joined: 7. Jan 2008, 16:17

Re: Solaris 11.1 VirtualBox USB issues with client Win7

Post by Ramshankar »

Oracle Corp.
Guyver
Posts: 104
Joined: 11. Feb 2012, 06:19
Primary OS: Solaris
VBox Version: PUEL
Guest OSses: Windows 7
Location: Central United States

Re: Solaris 11.1 VirtualBox USB issues with client Win7

Post by Guyver »

I most certainly will test it.

Downloading now.
Guyver
Posts: 104
Joined: 11. Feb 2012, 06:19
Primary OS: Solaris
VBox Version: PUEL
Guest OSses: Windows 7
Location: Central United States

Re: Solaris 11.1 VirtualBox USB issues with client Win7

Post by Guyver »

I received the following error when attempting to boot my win7 vmachine


Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Console
Interface:
IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}

log extract shows..

00:00:00.890292 VMSetError: /home/vbox/tinderbox/sol-rel/src/VBox/VMM/VMMR3/VM.cpp(364) int VMR3Create(uint32_t, const VMM2USERMETHODS*, void (*)(UVM*, void*, int, const char*, unsigned int, const char*, const char*, __va_list_tag*), void*, int (*)(UVM*, VM*, void*), void*, VM**, UVM**); rc=VERR_PDM_UNKNOWN_DEVREG_VERSION
00:00:00.890297 VMSetError: The version of the device registration structure is unknown to this VBox version. Either mixing incompatible versions or the structure isn't correctly initialized.
00:00:00.891006 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The version of the device registration structure is unknown to this VBox version. Either mixing incompatible versions or the structure isn't correctly initialized. (VERR_PDM_UNKNOWN_DEVREG_VERSION)}, preserve=false
00:00:00.915840 Power up failed (vrc=VERR_PDM_UNKNOWN_DEVREG_VERSION, rc=NS_ERROR_FAILURE (0X80004005))
Ramshankar
Oracle Corporation
Posts: 793
Joined: 7. Jan 2008, 16:17

Re: Solaris 11.1 VirtualBox USB issues with client Win7

Post by Ramshankar »

I think I need to provide you with a matching ExtPack for that build... Will try to upload one soon. Sorry for the trouble and thanks for trying it anyway.
Oracle Corp.
Ramshankar
Oracle Corporation
Posts: 793
Joined: 7. Jan 2008, 16:17

Re: Solaris 11.1 VirtualBox USB issues with client Win7

Post by Ramshankar »

Oracle Corp.
Guyver
Posts: 104
Joined: 11. Feb 2012, 06:19
Primary OS: Solaris
VBox Version: PUEL
Guest OSses: Windows 7
Location: Central United States

Re: Solaris 11.1 VirtualBox USB issues with client Win7

Post by Guyver »

Thanks for the extpack, that allowed the VM to boot.

Some USB devices, like the fingerprint scanner and built-in webcam are now functional.

The Broadcomm I'm still having difficulties with, but will try a full hardware poweroff, poweron and boot and get fresh vbox/messages log entries.

What I'm seeing is the broadcomm bluetooth device is somehow attaching/detaching rapidly - but again, will try again tomorrow.

Some progress is definitely better than none.
Guyver
Posts: 104
Joined: 11. Feb 2012, 06:19
Primary OS: Solaris
VBox Version: PUEL
Guest OSses: Windows 7
Location: Central United States

Re: Solaris 11.1 VirtualBox USB issues with client Win7

Post by Guyver »

Okay, when I bring up the VM with the broadcom device attached, I get the following errors in the VBox.log file...

Broadcom BCM20702A0 - I believe it's a Gen 4 bluetooth adapter.

Code: Select all

00:01:50.527851 EHCI: USB Operational
00:01:58.539777 EHCI: USB Suspended
00:01:59.981232 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:01:59.981271 USBProxy:usbProxySolarisReset failed. rc=-1
00:02:24.690578 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:02:24.690778 USBProxy:usbProxySolarisReset failed. rc=-1
00:02:48.911004 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:02:48.911085 USBProxy:usbProxySolarisReset failed. rc=-1
00:03:12.640859 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:03:12.640945 USBProxy:usbProxySolarisReset failed. rc=-1
00:03:36.390476 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:03:36.390540 USBProxy:usbProxySolarisReset failed. rc=-1
00:04:00.060593 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:04:00.060662 USBProxy:usbProxySolarisReset failed. rc=-1
00:04:23.830507 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:04:23.830561 USBProxy:usbProxySolarisReset failed. rc=-1
00:04:47.610757 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:04:47.610806 USBProxy:usbProxySolarisReset failed. rc=-1
The device attaches/detaches - detects the device, starts to install drivers, detaches, message about device missing in windows...

From the system messages file....

Code: Select all

Aug 14 08:48:47 nurb5088250 usba: [ID 691482 kern.warning] WARNING: /pci@0,0/pci17aa,21f6@1a/hub@1 (hubd0): Connecting device on port 4 failed
Aug 14 08:51:58 nurb5088250 last message repeated 8 times
Aug 14 08:52:22 nurb5088250 usba: [ID 691482 kern.warning] WARNING: /pci@0,0/pci17aa,21f6@1a/hub@1 (hubd0): Connecting device on port 4 failed
Aug 14 08:57:06 nurb5088250 last message repeated 12 times
These error messages (along with the usb device attached / detached bleeps in the windows vm) continue until I detach the device.

Unfortunately, when I detach the device, it hangs the VM for a bit, then the VM dies.

Code: Select all

00:01:59.981232 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:01:59.981271 USBProxy:usbProxySolarisReset failed. rc=-1
00:02:24.690578 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:02:24.690778 USBProxy:usbProxySolarisReset failed. rc=-1
00:02:48.911004 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:02:48.911085 USBProxy:usbProxySolarisReset failed. rc=-1
00:03:12.640859 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:03:12.640945 USBProxy:usbProxySolarisReset failed. rc=-1
00:03:36.390476 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:03:36.390540 USBProxy:usbProxySolarisReset failed. rc=-1
00:04:00.060593 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:04:00.060662 USBProxy:usbProxySolarisReset failed. rc=-1
00:04:23.830507 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:04:23.830561 USBProxy:usbProxySolarisReset failed. rc=-1
00:04:47.610757 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:04:47.610806 USBProxy:usbProxySolarisReset failed. rc=-1
00:05:11.340753 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:05:11.340806 USBProxy:usbProxySolarisReset failed. rc=-1
00:05:35.010748 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:05:35.010793 USBProxy:usbProxySolarisReset failed. rc=-1
00:05:58.680751 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:05:58.680802 USBProxy:usbProxySolarisReset failed. rc=-1
00:06:22.360663 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:06:22.360719 USBProxy:usbProxySolarisReset failed. rc=-1
00:06:46.040789 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:06:46.040840 USBProxy:usbProxySolarisReset failed. rc=-1
00:07:09.720665 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:07:09.720722 USBProxy:usbProxySolarisReset failed. rc=-1
00:07:33.400695 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:07:33.400747 USBProxy:usbProxySolarisReset failed. rc=-1
00:07:57.100740 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:07:57.100791 USBProxy:usbProxySolarisReset failed. rc=-1
00:08:20.800678 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:08:20.800732 USBProxy:usbProxySolarisReset failed. rc=-1
00:08:44.530677 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:08:44.530729 USBProxy:usbProxySolarisReset failed. rc=-1
00:09:08.210422 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:09:08.210474 USBProxy:usbProxySolarisReset failed. rc=-1
00:09:31.900576 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:09:31.900632 USBProxy:usbProxySolarisReset failed. rc=-1
00:09:55.600503 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:09:55.600551 USBProxy:usbProxySolarisReset failed. rc=-1
00:10:04.018952 VUSB: detached '00000000033a3e60[proxy 0a5c:21e6]' from port 2
00:10:19.300480 USBProxy:Command 0xc0185699 failed. Req.rc=VERR_GENERAL_FAILURE
00:10:19.300531 USBProxy:usbProxySolarisReset failed. rc=-1
00:10:19.300590 
00:10:19.300590 !!Assertion Failed!!
00:10:19.300591 Expression: RT_SUCCESS_NP(rc2)
00:10:19.300591 Location  : /home/vbox/tinderbox/sol-rel/src/VBox/Devices/USB/VUSBDevice.cpp(1318) int vusbDevResetThread(RTTHREADINT*, void*)
00:10:19.300784 VERR_TM_UNKNOWN_STATE (-2202) - The timer was in a unknown state. Corruption or stupid coding error.
Love the commentary in the last log line :)
Ramshankar
Oracle Corporation
Posts: 793
Joined: 7. Jan 2008, 16:17

Re: Solaris 11.1 VirtualBox USB issues with client Win7

Post by Ramshankar »

Thanks for testing and that does indeed look interesting :)

I'll try to see what's going on, in the mean time, can you confirm that those bulk xfer errors and devices dropping in and out of the VM is gone now?
Oracle Corp.
Guyver
Posts: 104
Joined: 11. Feb 2012, 06:19
Primary OS: Solaris
VBox Version: PUEL
Guest OSses: Windows 7
Location: Central United States

Re: Solaris 11.1 VirtualBox USB issues with client Win7

Post by Guyver »

Confirmed. Bulk xfer messages gone.

Some devices are stable, some like the Broadcom bluetooth are still dropping in/out as descrbed above.
Guyver
Posts: 104
Joined: 11. Feb 2012, 06:19
Primary OS: Solaris
VBox Version: PUEL
Guest OSses: Windows 7
Location: Central United States

Re: Solaris 11.1 VirtualBox USB issues with client Win7

Post by Guyver »

Also noticed the new "message" bars popping up.
Interesting that they are claiming that the VM requires 32bpp, then complain that I'm using x-windows color depth 24 (which is 32bpp)... odd wouldn't you say?
Post Reply