USB 3.0 hard drive fails to appear in guest when in 3.0 port
Posted: 15. Apr 2012, 17:39
I have a USB 3.0 hard drive that doesn't appear in the guest OS (both Host and Guest are Ubuntu Linux) when it is plugged into the USB 3.0 port on the motherboard. However, if I plug it into one of the USB 2.0 ports it works fine. Here is the dmesg from the guest when it is plugged into the USB 3.0 port:
[ 195.452122] usb 1-1: new high speed USB device number 6 using ehci_hcd
[ 195.600107] usb 1-1: device descriptor read/64, error 18
[ 195.844117] usb 1-1: device descriptor read/64, error 18
[ 196.060115] usb 1-1: new high speed USB device number 7 using ehci_hcd
[ 196.208112] usb 1-1: device descriptor read/64, error 18
[ 196.452987] usb 1-1: device descriptor read/64, error 18
[ 196.668108] usb 1-1: new high speed USB device number 8 using ehci_hcd
[ 196.736410] usb 1-1: Invalid ep0 maxpacket: 9
[ 196.852103] usb 1-1: new high speed USB device number 9 using ehci_hcd
[ 196.911949] usb 1-1: Invalid ep0 maxpacket: 9
[ 196.916099] hub 1-0:1.0: unable to enumerate USB device on port 1
The drive works correctly when plugged into the USB 3.0 port with the Host OS (no USB filter for it in VirtualBox).
Should I report this as a bug or am I missing something?
[ 195.452122] usb 1-1: new high speed USB device number 6 using ehci_hcd
[ 195.600107] usb 1-1: device descriptor read/64, error 18
[ 195.844117] usb 1-1: device descriptor read/64, error 18
[ 196.060115] usb 1-1: new high speed USB device number 7 using ehci_hcd
[ 196.208112] usb 1-1: device descriptor read/64, error 18
[ 196.452987] usb 1-1: device descriptor read/64, error 18
[ 196.668108] usb 1-1: new high speed USB device number 8 using ehci_hcd
[ 196.736410] usb 1-1: Invalid ep0 maxpacket: 9
[ 196.852103] usb 1-1: new high speed USB device number 9 using ehci_hcd
[ 196.911949] usb 1-1: Invalid ep0 maxpacket: 9
[ 196.916099] hub 1-0:1.0: unable to enumerate USB device on port 1
The drive works correctly when plugged into the USB 3.0 port with the Host OS (no USB filter for it in VirtualBox).
Should I report this as a bug or am I missing something?