USB 3 on Linux Guests with Windows Hosts

Discussions related to using VirtualBox on Windows hosts.
jschwartzman
Posts: 5
Joined: 30. Jun 2011, 23:12
Primary OS: MS Windows 10
VBox Version: OSE other
Guest OSses: opensuse - TUMBLEWEED

Re: USB 3 on Linux Guests with Windows Hosts

Post by jschwartzman »

I've attached the log file.
Attachments
VBox.7z
(21.74 KiB) Downloaded 9 times
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: USB 3 on Linux Guests with Windows Hosts

Post by mpack »

Ok, the extension pack is installed, so that is not the problem.

I see this in the log.
00:00:53.790431 VUSB: Attached '0000000003e23870[proxy 154b:00ed]' to port 1 on RootHub#1 (HighSpeed)
00:01:09.032021 VUSB: Detached '0000000003e23870[proxy 154b:00ed]' from port 1 on RootHub#1
So, device was attached, then detached 16 seconds later. I'd say that the feature is working - as least far as the VM is concerned. Perhaps your problem is an incorrectly configured guest OS, e.g. no guest driver, or your user not added to the "vboxusers" group.
jschwartzman
Posts: 5
Joined: 30. Jun 2011, 23:12
Primary OS: MS Windows 10
VBox Version: OSE other
Guest OSses: opensuse - TUMBLEWEED

Re: USB 3 on Linux Guests with Windows Hosts

Post by jschwartzman »

My user is a member of the vboxuser group. I'm not sure about the driver; how can I check? Do I have the latest version of guest additions? How can I check?

Thanks,
John
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: USB 3 on Linux Guests with Windows Hosts

Post by mpack »

Sorry, I can't tell you how to install the driver for your USB device. Check the instructions I guess.

I see no evidence that you've installed any Guest Additions, but no matter since they aren't relevant to USB anyway. Your extension pack is the correct version.
TomInAustin
Posts: 1
Joined: 14. Sep 2018, 00:14

Re: USB 3 on Linux Guests with Windows Hosts

Post by TomInAustin »

I'm experiencing the same issue.
System:
Host: Windows 10
Guest: CentOS 7
VirtualBox: 5.2.18
External Drives:
2TB Seagate, USB 3.0, ext4, Accessible by the VM
3TB WD, USB 3.0, ext4, NOT accessible by the VM

When the drives are plugged in, but not yet "attached" to the VM (i.e., Devices->USB), VBoxManage.exe list usbhost yields

Code: Select all

UUID:               02a5dee3-0284-43b2-b9e1-c4acb9d4156a
VendorId:           0x0bc2 (0BC2)
ProductId:          0xab24 (AB24)
Revision:           1.0 (0100)
Port:               2
USB version/speed:  3/Super
Manufacturer:       Seagate
Product:            BUP Slim SL
SerialNumber:       NA9JQRKJ
Address:            {4d36e97b-e325-11ce-bfc1-08002be10318}\0006
Current State:      Busy

UUID:               6c7a5f5e-45e5-4822-a3d8-1ef19fe98a81
VendorId:           0x1058 (1058)
ProductId:          0x25e2 (25E2)
Revision:           64.5 (6405)
Port:               17
USB version/speed:  3/Super
Manufacturer:       Western Digital
Product:            My Passport 25E2
SerialNumber:       575834314441374436383352
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0050
Current State:      Busy
When the drives are "attached" to the VM, VBoxManage.exe list usbhost yields

Code: Select all

UUID:               02a5dee3-0284-43b2-b9e1-c4acb9d4156a
VendorId:           0x0bc2 (0BC2)
ProductId:          0xab24 (AB24)
Revision:           1.0 (0100)
Port:               2
USB version/speed:  3/Super
Manufacturer:       Seagate
Product:            BUP Slim SL
SerialNumber:       NA9JQRKJ
Address:            \\?\usb#vid_80ee&pid_cafe#msft30na9jqrkj#{00873fdf-cafe-80ee-aa5e-00c04fb1720b}
Current State:      Captured

UUID:               6c7a5f5e-45e5-4822-a3d8-1ef19fe98a81
VendorId:           0x1058 (1058)
ProductId:          0x25e2 (25E2)
Revision:           64.5 (6405)
Port:               17
USB version/speed:  3/High
Manufacturer:       Western Digital
Product:            My Passport 25E2
SerialNumber:       575834314441374436383352
Address:            \\?\usb#vid_80ee&pid_cafe#575834314441374436383352#{00873fdf-cafe-80ee-aa5e-00c04fb1720b}
Current State:      Captured
Note that the non-available WD drive went from being recognized as a SuperSpeed drive to a High Speed drive. Note, also, that both of these drives are recognized and mountable on standard (non-VM) CentOS-7 systems (and work at SuperSpeed rates). I don't know what this means but I hope it points to where the issue may be.
Attachments
CentOS-7-2018-09-13-18-00-50.log
(101.09 KiB) Downloaded 6 times
Post Reply