Sadly I'm having the same exact issue, and the link expired. Can I get a copy of that module please?Ramshankar wrote:Unfortunately, yes. Keep the custom build driver.Guyver wrote:Have since upgraded to 4.3.2, should I still be using that special build vboxusb driver?
Solaris 11.1 VirtualBox USB issues with client Win7
-
- Posts: 6
- Joined: 2. Dec 2013, 07:14
- Primary OS: Solaris
- VBox Version: PUEL
- Guest OSses: Linux,Windows,NetBSD
Re: Solaris 11.1 VirtualBox USB issues with client Win7
-
- Oracle Corporation
- Posts: 793
- Joined: 7. Jan 2008, 16:17
Re: Solaris 11.1 VirtualBox USB issues with client Win7
Here you go: https://www.virtualbox.org/download/tes ... _sol64.zip
Instruction on how to install, see this post: viewtopic.php?f=11&t=55816&start=15#p268335 (follow from point 2 in that post, the info. above that is irrelevant)
Instruction on how to install, see this post: viewtopic.php?f=11&t=55816&start=15#p268335 (follow from point 2 in that post, the info. above that is irrelevant)
Oracle Corp.
-
- Posts: 6
- Joined: 2. Dec 2013, 07:14
- Primary OS: Solaris
- VBox Version: PUEL
- Guest OSses: Linux,Windows,NetBSD
Re: Solaris 11.1 VirtualBox USB issues with client Win7
Ramshankar,Ramshankar wrote:Here you go: https://www.virtualbox.org/download/tes ... _sol64.zip
Instruction on how to install, see this post: viewtopic.php?f=11&t=55816&start=15#p268335 (follow from point 2 in that post, the info. above that is irrelevant)
Just wanted to say thanks. This works perfectly on Solaris 11.1.13.6.0 & VirtualBox 4.3.4!
Any hopes of seeing this merged into the official product?
-
- 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
Okay - finally had a few moments to do some additional testing...
Using latest Soliars 11 release - 11.1.13.6.0
Using latest VirtualBox release - 4.3.4r91027
Using the vboxusb driver you provided.
Booted the windows 7 VM, attached the Blackberry phone, started the blackberry desktop software, off it went to "initializing device" screen with the nice spinning icon... There it sat indefinitely...
On the Solaris side, we see the following...
Dec 9 14:55:49 nurb5088250 genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,21f6@14/device@1 (usb_mid4) online
Dec 9 14:55:49 nurb5088250 genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,21f6@14/device@1/storage@1/disk@0,0 (sd5) removed
Dec 9 14:55:49 nurb5088250 genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,21f6@14/device@1/storage@1/disk@0,1 (sd6) removed
Dec 9 14:55:49 nurb5088250 genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,21f6@14/device@1/storage@1 (scsa2usb3) removed
Dec 9 14:55:49 nurb5088250 genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,21f6@14/device@1 (usb_mid4) removed
Dec 9 14:55:50 nurb5088250 genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,21f6@14/device@1 (vboxusb3) online
All good, transferring blackberry device control to the VirtualBox VM...
20 minutes into the initialization process, we get
Dec 9 15:15:34 nurb5088250 fmd: [ID 377184 daemon.error] SUNW-MSG-ID: USB-8000-2W, TYPE: Fault, VER: 1, SEVERITY: Major
Dec 9 15:15:34 nurb5088250 EVENT-TIME: Mon Dec 9 15:15:34 CST 2013
Dec 9 15:15:34 nurb5088250 PLATFORM: 24294Y2, CSN: R9YZLBK, HOSTNAME: REDACTED
Dec 9 15:15:34 nurb5088250 SOURCE: eft, REV: 1.16
Dec 9 15:15:34 nurb5088250 EVENT-ID: 136cb9fb-7f40-6032-db55-91e730f8c2a8
Dec 9 15:15:34 nurb5088250 DESC: A packet timeout was detected in the USB device and the corresponding driver may not be able to recover from the errors automatically.
Dec 9 15:15:34 nurb5088250 AUTO-RESPONSE: Device may have been disabled or may not be fully functional.
Dec 9 15:15:34 nurb5088250 IMPACT: Loss of services provided by the device instances associated with this fault.
Dec 9 15:15:34 nurb5088250 REC-ACTION: Use 'fmadm faulty' to provide a more detailed view of this event. Please refer to the associated reference document at http://support.oracle.com/msg/USB-8000-2W for the latest service procedures and policies regarding this diagnosis.
fmadm faulty gives us the following...
--------------- ------------------------------------ -------------- ---------
TIME EVENT-ID MSG-ID SEVERITY
--------------- ------------------------------------ -------------- ---------
Dec 09 15:15:34 136cb9fb-7f40-6032-db55-91e730f8c2a8 USB-8000-2W Major
Problem Status : solved
Diag Engine : eft / 1.16
System
Manufacturer : Intel_ASF
Name : Intel_ASF
Part_Number : Intel_ASF_001
Serial_Number : Intel_ASF
System Component
Manufacturer : LENOVO
Name : 24294Y2
Part_Number : LENOVO_MT_2429
Serial_Number : R9YZLBK
Host_ID : 00cff30c
----------------------------------------
Suspect 1 of 1 :
Fault class : fault.io.usb.pto
Certainty : 100%
Affects : dev:////pci@0,0/pci17aa,21f6@14/device@1
Status : faulted but still in service
FRU
Name : "hc://:chassis-mfg=LENOVO:chassis-name=Not-Available:chassis-part=No-Asset-Information:chassis-serial=R9YZLBK:fru-serial=127E13DD3F3D2845B82C9169655CCE11FFFF58F0:fru-part=8007-0fca/motherboard=0/hostbridge=0/usb-bus=0/usbdev=1"
Manufacturer : unknown
Name : unknown
Part_Number : 8007-0fca
Revision : unknown
Serial_Number : 127E13DD3F3D2845B82C9169655CCE11FFFF58F0
Chassis
Manufacturer : LENOVO
Name : Not-Available
Part_Number : No-Asset-Information
Serial_Number : R9YZLBK
Status : faulty
Description : A packet timeout was detected in the USB device and the
corresponding driver may not be able to recover from the errors
automatically.
Response : Device may have been disabled or may not be fully functional.
Impact : Loss of services provided by the device instances associated with
this fault.
Action : Use 'fmadm faulty' to provide a more detailed view of this event.
Please refer to the associated reference document at
http://support.oracle.com/msg/USB-8000-2W for the latest service
procedures and policies regarding this diagnosis.
Using latest Soliars 11 release - 11.1.13.6.0
Using latest VirtualBox release - 4.3.4r91027
Using the vboxusb driver you provided.
Booted the windows 7 VM, attached the Blackberry phone, started the blackberry desktop software, off it went to "initializing device" screen with the nice spinning icon... There it sat indefinitely...
On the Solaris side, we see the following...
Dec 9 14:55:49 nurb5088250 genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,21f6@14/device@1 (usb_mid4) online
Dec 9 14:55:49 nurb5088250 genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,21f6@14/device@1/storage@1/disk@0,0 (sd5) removed
Dec 9 14:55:49 nurb5088250 genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,21f6@14/device@1/storage@1/disk@0,1 (sd6) removed
Dec 9 14:55:49 nurb5088250 genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,21f6@14/device@1/storage@1 (scsa2usb3) removed
Dec 9 14:55:49 nurb5088250 genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,21f6@14/device@1 (usb_mid4) removed
Dec 9 14:55:50 nurb5088250 genunix: [ID 408114 kern.info] /pci@0,0/pci17aa,21f6@14/device@1 (vboxusb3) online
All good, transferring blackberry device control to the VirtualBox VM...
20 minutes into the initialization process, we get
Dec 9 15:15:34 nurb5088250 fmd: [ID 377184 daemon.error] SUNW-MSG-ID: USB-8000-2W, TYPE: Fault, VER: 1, SEVERITY: Major
Dec 9 15:15:34 nurb5088250 EVENT-TIME: Mon Dec 9 15:15:34 CST 2013
Dec 9 15:15:34 nurb5088250 PLATFORM: 24294Y2, CSN: R9YZLBK, HOSTNAME: REDACTED
Dec 9 15:15:34 nurb5088250 SOURCE: eft, REV: 1.16
Dec 9 15:15:34 nurb5088250 EVENT-ID: 136cb9fb-7f40-6032-db55-91e730f8c2a8
Dec 9 15:15:34 nurb5088250 DESC: A packet timeout was detected in the USB device and the corresponding driver may not be able to recover from the errors automatically.
Dec 9 15:15:34 nurb5088250 AUTO-RESPONSE: Device may have been disabled or may not be fully functional.
Dec 9 15:15:34 nurb5088250 IMPACT: Loss of services provided by the device instances associated with this fault.
Dec 9 15:15:34 nurb5088250 REC-ACTION: Use 'fmadm faulty' to provide a more detailed view of this event. Please refer to the associated reference document at http://support.oracle.com/msg/USB-8000-2W for the latest service procedures and policies regarding this diagnosis.
fmadm faulty gives us the following...
--------------- ------------------------------------ -------------- ---------
TIME EVENT-ID MSG-ID SEVERITY
--------------- ------------------------------------ -------------- ---------
Dec 09 15:15:34 136cb9fb-7f40-6032-db55-91e730f8c2a8 USB-8000-2W Major
Problem Status : solved
Diag Engine : eft / 1.16
System
Manufacturer : Intel_ASF
Name : Intel_ASF
Part_Number : Intel_ASF_001
Serial_Number : Intel_ASF
System Component
Manufacturer : LENOVO
Name : 24294Y2
Part_Number : LENOVO_MT_2429
Serial_Number : R9YZLBK
Host_ID : 00cff30c
----------------------------------------
Suspect 1 of 1 :
Fault class : fault.io.usb.pto
Certainty : 100%
Affects : dev:////pci@0,0/pci17aa,21f6@14/device@1
Status : faulted but still in service
FRU
Name : "hc://:chassis-mfg=LENOVO:chassis-name=Not-Available:chassis-part=No-Asset-Information:chassis-serial=R9YZLBK:fru-serial=127E13DD3F3D2845B82C9169655CCE11FFFF58F0:fru-part=8007-0fca/motherboard=0/hostbridge=0/usb-bus=0/usbdev=1"
Manufacturer : unknown
Name : unknown
Part_Number : 8007-0fca
Revision : unknown
Serial_Number : 127E13DD3F3D2845B82C9169655CCE11FFFF58F0
Chassis
Manufacturer : LENOVO
Name : Not-Available
Part_Number : No-Asset-Information
Serial_Number : R9YZLBK
Status : faulty
Description : A packet timeout was detected in the USB device and the
corresponding driver may not be able to recover from the errors
automatically.
Response : Device may have been disabled or may not be fully functional.
Impact : Loss of services provided by the device instances associated with
this fault.
Action : Use 'fmadm faulty' to provide a more detailed view of this event.
Please refer to the associated reference document at
http://support.oracle.com/msg/USB-8000-2W for the latest service
procedures and policies regarding this diagnosis.
Re: Solaris 11.1 VirtualBox USB issues with client Win7
Ram,
Would you mind sharing the vbox usb driver again? It seems, that link provided is expired.
I am running Solaris 11.1 host with Win XP as guest with VBox 4.3.6. I assumed this might have been fixed in recent Vbox build, as it is reported a while ago. But now I tracked this thread, I need same fix. (USB worked fine on Solaris 11 Express).
Appreciate help!
Thanks
Chinna
Would you mind sharing the vbox usb driver again? It seems, that link provided is expired.
I am running Solaris 11.1 host with Win XP as guest with VBox 4.3.6. I assumed this might have been fixed in recent Vbox build, as it is reported a while ago. But now I tracked this thread, I need same fix. (USB worked fine on Solaris 11 Express).
Appreciate help!
Thanks
Chinna
-
- Oracle Corporation
- Posts: 793
- Joined: 7. Jan 2008, 16:17
Re: Solaris 11.1 VirtualBox USB issues with client Win7
Sorry for the late response.
Here you go: https://www.virtualbox.org/download/tes ... 64_sol.zip
Instruction on how to install, see this post: viewtopic.php?f=11&t=55816&start=15#p268335 (follow from point 2 in that post, the info. above that is irrelevant, i.e. you can use it with VirtualBox 4.3.x versions, not just RC1 as mentioned in that post)
Here you go: https://www.virtualbox.org/download/tes ... 64_sol.zip
Instruction on how to install, see this post: viewtopic.php?f=11&t=55816&start=15#p268335 (follow from point 2 in that post, the info. above that is irrelevant, i.e. you can use it with VirtualBox 4.3.x versions, not just RC1 as mentioned in that post)
Oracle Corp.
-
- 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
Unfortunately, I'm still having issues with USB devices being accessible by the Windows 7 guest OS.
Perhaps it's the rev of my Intel Chipset or something like that. Waiting for Solaris 11.2 to be released to see if it fixes my usb issues.
For now, it's no usb devices for Windows 7.
Perhaps it's the rev of my Intel Chipset or something like that. Waiting for Solaris 11.2 to be released to see if it fixes my usb issues.
For now, it's no usb devices for Windows 7.
-
- Posts: 2
- Joined: 31. Mar 2014, 20:08
Re: Solaris 11.1 VirtualBox USB issues with client Win7
Is the driver issue still relevant for 11.1 & 4.3.10?
because I'm also having this issue and would like to try this fix.
because I'm also having this issue and would like to try this fix.
-
- Posts: 6
- Joined: 2. Dec 2013, 07:14
- Primary OS: Solaris
- VBox Version: PUEL
- Guest OSses: Linux,Windows,NetBSD
Re: Solaris 11.1 VirtualBox USB issues with client Win7
As far as I can tell, yes.ParadoxMoose wrote:Is the driver issue still relevant for 11.1 & 4.3.10?
because I'm also having this issue and would like to try this fix.
-
- Posts: 2
- Joined: 31. Mar 2014, 20:08
Re: Solaris 11.1 VirtualBox USB issues with client Win7
I really hope this either becomes a public release at some point or they repost the link, I would love to be able to use VB in my test environment.
Re: Solaris 11.1 VirtualBox USB issues with client Win7
Hello,
Could you possibly repost the link for latest VBOX release.
Thank you.
Magboro
Could you possibly repost the link for latest VBOX release.
Thank you.
Magboro
-
- Oracle Corporation
- Posts: 793
- Joined: 7. Jan 2008, 16:17
Re: Solaris 11.1 VirtualBox USB issues with client Win7
https://www.virtualbox.org/download/tes ... 83_rel.zip
Instruction on how to install, see this post: viewtopic.php?f=11&t=55816&start=15#p268335 (follow from point 2 in that post, the info. above that is irrelevant, i.e. you can use it with VirtualBox 4.3.x versions, not just RC1 as mentioned in that post)
Instruction on how to install, see this post: viewtopic.php?f=11&t=55816&start=15#p268335 (follow from point 2 in that post, the info. above that is irrelevant, i.e. you can use it with VirtualBox 4.3.x versions, not just RC1 as mentioned in that post)
Oracle Corp.
Re: Solaris 11.1 VirtualBox USB issues with client Win7
The link isn't valid anymore. Please provide new download link.
Thanks,
Mike.
Thanks,
Mike.