[Solved] Problem with USB device

Discussions related to using VirtualBox on Windows hosts.

[Solved] Problem with USB device

Postby roberto76 » 24. May 2019, 13:52

I cannot use USB devices in my VirtualBox guests.
I've read carefully the troubleshooting and tried everything I could think, but without success.
So now I'm asking help in the forum.

Thanks to everyone

Host:
Code: Select all   Expand viewCollapse view
Windows 10 Pro 1809 - 02/04/2019 - Build 17763.503

Guest:
Code: Select all   Expand viewCollapse view
NAME="Ubuntu"
VERSION="18.04.2 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.2 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
Linux TI-SDK-64bit 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Command:
Code: Select all   Expand viewCollapse view
C:\Program Files\Oracle\VirtualBox>VBoxManage list usbhost
Host USB Devices:

UUID:               34086c92-17f6-41ae-a5f2-c5509aaf6e2f
VendorId:           0x8087 (8087)
ProductId:          0x0a2a (0A2A)
Revision:           0.1 (0001)
Port:               8
USB version/speed:  2/Full
Manufacturer:       Intel Corp.
Address:            {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}\0000
Current State:      Busy

UUID:               65621cee-34f6-42df-878c-919f8a5233b8
VendorId:           0x0bda (0BDA)
ProductId:          0x57ed (57ED)
Revision:           0.1 (0001)
Port:               6
USB version/speed:  2/High
Manufacturer:       Realtek Semiconductor Corp.
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0003
Current State:      Busy

UUID:               cf5cffda-076d-49cf-aaec-4d7e7b4eca30
VendorId:           0x067b (067B)
ProductId:          0x2303 (2303)
Revision:           4.0 (0400)
Port:               3
USB version/speed:  1/Full
Manufacturer:       Prolific Technology Inc.
Product:            USB-Serial Controller D
Address:            {4d36e978-e325-11ce-bfc1-08002be10318}\0000
Current State:      Busy

UUID:               cc544002-6b68-4cb0-ba7c-5ffb9269ae51
VendorId:           0x0461 (0461)
ProductId:          0x4d0f (4D0F)
Revision:           1.0 (0100)
Port:               1
USB version/speed:  2/Low
Manufacturer:       PixArt
Product:            USB Optical Mouse
Address:            {745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0017
Current State:      Busy

UUID:               cabaec91-f3a5-46c0-8fe0-7a39fbf30c91
VendorId:           0x0461 (0461)
ProductId:          0x0010 (0010)
Revision:           1.4 (0104)
Port:               4
USB version/speed:  1/Low
Manufacturer:       NOVATEK
Product:            USB Keyboard
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0018
Current State:      Busy

Code: Select all   Expand viewCollapse view
C:\Program Files\Oracle\VirtualBox>VBoxManage list usbfilters
Global USB Device Filters:

<none>

Code: Select all   Expand viewCollapse view
C:\Program Files\Oracle\VirtualBox>VBoxManage showvminfo "Signal SDK 64-bit"
Name:                        Signal SDK 64-bit
Groups:                      /
Guest OS:                    Ubuntu (64-bit)
UUID:                        5ee7f02a-22c0-41ea-8a4c-5d5900c51248
Config file:                 C:\Users\r.chiarini\VirtualBox VMs\Signal SDK 64-bit\Signal SDK 64-bit.vbox
Snapshot folder:             C:\Users\r.chiarini\VirtualBox VMs\Signal SDK 64-bit\Snapshots
Log folder:                  C:\Users\r.chiarini\VirtualBox VMs\Signal SDK 64-bit\Logs
Hardware UUID:               5ee7f02a-22c0-41ea-8a4c-5d5900c51248
Memory size                  2048MB
Page Fusion:                 disabled
VRAM size:                   32MB
CPU exec cap:                100%
HPET:                        disabled
CPUProfile:                  host
Chipset:                     piix3
Firmware:                    BIOS
Number of CPUs:              1
PAE:                         enabled
Long Mode:                   enabled
Triple Fault Reset:          disabled
APIC:                        enabled
X2APIC:                      enabled
Nested VT-x/AMD-V:           disabled
CPUID Portability Level:     0
CPUID overrides:             None
Boot menu mode:              message and menu
Boot Device 1:               Floppy
Boot Device 2:               DVD
Boot Device 3:               HardDisk
Boot Device 4:               Not Assigned
ACPI:                        enabled
IOAPIC:                      enabled
BIOS APIC mode:              APIC
Time offset:                 0ms
RTC:                         UTC
Hardw. virt.ext:             enabled
Nested Paging:               enabled
Large Pages:                 enabled
VT-x VPID:                   enabled
VT-x unr. exec.:             enabled
Paravirt. Provider:          Default
Effective Paravirt. Prov.:   KVM
State:                       powered off (since 2019-05-24T10:28:07.000000000)
Monitor count:               1
3D Acceleration:             enabled
2D Video Acceleration:       disabled
Teleporter Enabled:          disabled
Teleporter Port:             0
Teleporter Address:
Teleporter Password:
Tracing Enabled:             disabled
Allow Tracing to Access VM:  disabled
Tracing Configuration:
Autostart Enabled:           disabled
Autostart Delay:             0
Default Frontend:
Storage Controller Name (0):            IDE
Storage Controller Type (0):            PIIX3
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):            SATA
Storage Controller Type (1):            IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  30
Storage Controller Port Count (1):      4
Storage Controller Bootable (1):        on
IDE (1, 0): Empty
SATA (0, 0): D:\VMs\Signal_SDK_64-bit_disk1.vdi (UUID: d361030d-1fbf-4770-90ed-8749d2390ac5)
SATA (1, 0): D:\VMs\Signal_SDK_64-bit_disk2.vdi (UUID: 7e4cba5e-e29f-4ae3-b33e-9715f254d829)
SATA (2, 0): D:\VMs\Signal_SDK_64-bit_disk3.vdi (UUID: 422a507c-4535-451f-b59c-aebfe8e4e858)
NIC 1:                       MAC: 080027A93C6A, Attachment: Bridged Interface 'Realtek PCIe GBE Family Controller', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, 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
UART 3:                      disabled
UART 4:                      disabled
LPT 1:                       disabled
LPT 2:                       disabled
Audio:                       disabled
Audio playback:              enabled
Audio capture:               enabled
Clipboard Mode:              Bidirectional
Drag and drop Mode:          Bidirectional
VRDE:                        disabled
OHCI USB:                    disabled
EHCI USB:                    disabled
xHCI USB:                    enabled

USB Device Filters:

Index:                       0
Active:                      yes
Name:                        Prolific Technology Inc. USB-Serial Controller D [0400]
VendorId:                    067b
ProductId:                   2303
Revision:
Manufacturer:
Product:
Remote:
Serial Number:

Bandwidth groups:  <none>

Shared folders:

Name: 'C_DRIVE', Host path: 'C:\' (machine mapping), writable, auto-mount
Name: 'H_DRIVE', Host path: 'H:\' (machine mapping), writable, auto-mount
Name: 'L_DRIVE', Host path: 'L:\' (machine mapping), writable, auto-mount
Name: 'Projects', Host path: 'D:\Projects' (machine mapping), writable, auto-mount
Name: 'X_DRIVE', Host path: 'X:\' (machine mapping), writable, auto-mount

Capturing:                   not active
Capture audio:               not active
Capture screens:             0
Capture file:                C:\Users\r.chiarini\VirtualBox VMs\Signal SDK 64-bit\Signal SDK 64-bit.webm
Capture dimensions:          1024x768
Capture rate:                512kbps
Capture FPS:                 25kbps
Capture options:             ac_enabled=false

Description:
Macchina virtuale di sviluppo su processore Sitara AM3352 con TI Processor SDK
Guest:

Configured memory balloon size: 0MB
Attachments
VBox.zip
Log file
(29.02 KiB) Downloaded 6 times
Last edited by socratis on 31. May 2019, 22:31, edited 3 times in total.
Reason: Marked as [Solved].
roberto76
 
Posts: 10
Joined: 24. Aug 2017, 08:37

Re: Problem with USB device

Postby socratis » 24. May 2019, 22:51

roberto76 wrote:I cannot use USB devices in my VirtualBox guests.

Any USB device? Or just the Prolific USB-to-serial? And what does it mean "cannot use"? You can't see the device in the guest? ALL the USB devices that you tried? What exactly?
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 24800
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Problem with USB device

Postby roberto76 » 27. May 2019, 08:16

Any USB device?

Yes. I tried a Prolific USB-RS232 Converter, some USB pen drive and some SD card reader, but the result is the same.

And what does it mean "cannot use"?

It means that USB devices work without any problem in my Windows 10 host and are available in drop-down list of the virtual machine.
When I try to pass the device to my Linux guest, I get no error, but it isn't available for the guest. Nothing changes using filters or on-the-fly modes.

I tried with two Linux guests (both are equipped with Ubuntu but different versions - 12 and 18).

I searched over the forum for a solution and I found two interesting links:
1) viewtopic.php?f=35&t=82639
2) viewtopic.php?f=6&t=39104#p176270
I followed the proposed solutions, but nothing works in my case.

I hope that now my problem is more clear.
roberto76
 
Posts: 10
Joined: 24. Aug 2017, 08:37

Re: Problem with USB device

Postby DenisF » 27. May 2019, 18:58

Hello,
I've the same mistake.
Host: Win10
Guest: Win7
VBoxManage list usbhost
UUID: d8b4441e-7a1c-4690-8251-59e0bbb711cc
VendorId: 0x16de (16DE)
ProductId: 0x0001 (0001)
Revision: 0.0 (0000)
Port: 3
USB version/speed: 2/Full
Product: Telemecanique BMX CPU
Current State: Captured

But Guest get nothing in device manager.
Last edited by socratis on 28. May 2019, 11:12, edited 1 time in total.
Reason: Enclosed the information in [quote][pre] tags for better readability
DenisF
 
Posts: 31
Joined: 16. May 2012, 15:00

Re: Problem with USB device

Postby socratis » 28. May 2019, 08:44

Can all of you try the latest 6.x test builds? It contains several fixes regarding the USB front...
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 24800
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Problem with USB device

Postby DenisF » 28. May 2019, 10:27

Hello,
Still not working with 6.0.9.130868.
I found that in .VirtualBox\VBoxSVC.log
00:03:52.913874 USBPROXY Getting USB descriptor failed with error 31
00:03:52.918941 USBPROXY USB: Unknown USB device detected (idVendor: 0x16de, idProduct: 0x0001)

Does VB need to know device before routing it to Guest?
Is it possible to have a pass-through option?
Last edited by socratis on 28. May 2019, 11:13, edited 1 time in total.
Reason: Enclosed the information in [quote][pre] tags for better readability
DenisF
 
Posts: 31
Joined: 16. May 2012, 15:00

Re: Problem with USB device

Postby socratis » 28. May 2019, 11:16

DenisF wrote:
Current State: Captured
Your USB device shows as "Captured", that means the guest has it. What do you see in the guest? Please read the following thread: USB basics and troubleshooting, all of the posts.

If you still have a problem after reading through the whole thing, please follow the advice of the last post, #8: Asking for help and post the information requested.

DenisF wrote:But Guest get nothing in device manager.
There are other tools besides the Device Manager. Check the link above. What kind of a USB device it this one?
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 24800
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Problem with USB device

Postby DenisF » 28. May 2019, 12:10

Running with linux guest, I've got the same.
VBoxManage says captured but lsusb show nothing.
And it is not checked in GUI.
DenisF
 
Posts: 31
Joined: 16. May 2012, 15:00

Re: Problem with USB device

Postby socratis » 28. May 2019, 12:14

Was my post difficult to read? Was it confusing?
socratis wrote:If you still have a problem after reading through the whole thing, please follow the advice of the last post, #8: Asking for help and post the information requested.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 24800
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Problem with USB device

Postby Horst_Mueller » 28. May 2019, 12:35

I want to reaffirm that I am seeing the same problem here:

All USB devices are being shown by VB and when trying to assign one to VB it shows as captured but seems not to actually be attached to the guest.

After closing VB, physically disconnecting the USB device and restarting VB again, the device is still visible in the VB USB device list.
Reconnecting to the physical USB port then results in this device being shown *twice*.

This seems not to dependent on the class of USB device, so far I tried a USB memory stick, a USB headset and a USB LAN adapter.
All are showing the same behaviour.

I also deinstalled the 6.0.8 VB release and tried 5.2.30 instead, but this is showing the same behaviour.
Also tried different guest VMs (Debian/Ubuntu), one of them freshly installed for this purpose (Debian 9 under VB 5.2.30): same behaviour.
It also seems to effect more then one Version of Win10, as I am running Release 18.03 as opposed to 18.09 that is used by the OP.

M VBoxSVC.log shows the "error 31" messages, but not the not the "Unknown USB device" messages, so these may be unrelated.

I read the troubleshooting in "USB basics and troubleshooting" and followed all given advice (e.g. I removed wireshark), but to no avail.


@socratis: I will collect the information you requested.

Which VB version should I use for the logs? 6.0.8, 6.0.9 or 5.2.30?
Horst_Mueller
 
Posts: 1
Joined: 28. May 2019, 11:57

Re: Problem with USB device

Postby socratis » 28. May 2019, 12:46

Horst_Mueller wrote:Which VB version should I use for the logs? 6.0.8, 6.0.9 or 5.2.30?

Try with the latest 6.0.97, the Development build, not the 6.0.x or the 5.2.x builds, the development one, that's where the USB problems have been addressed.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 24800
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Problem with USB device

Postby DenisF » 28. May 2019, 13:31

Is it normal that dev version seems to be more older(130867) than test one(130868)?
DenisF
 
Posts: 31
Joined: 16. May 2012, 15:00

Re: Problem with USB device

Postby socratis » 28. May 2019, 13:36

Yes. No problem there, the revisions depend on when they were built. Each build gets a sequential number. The developers can give the "build" command for the development and then for the pre-release/test builds resulting in what you're seeing. Under the hood however they contain different trees.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 24800
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Problem with USB device

Postby DenisF » 28. May 2019, 17:01

It's the same with 6.0.97...
DenisF
 
Posts: 31
Joined: 16. May 2012, 15:00

Re: Problem with USB device

Postby DenisF » 28. May 2019, 19:04

OK,
Got it working.
I have to remove default (not working) driver for my device in host device manager.
Then Virtual Box USB appears in list.

Then I see `VBoxManage list usbhost` with an Address
UUID:               d3c864d3-0897-44ef-b2e3-e983c8a4d53a
VendorId: 0x16de (16DE)
ProductId: 0x0001 (0001)
Revision: 0.0 (0000)
Port: 1
USB version/speed: 2/Full
Product: Telemecanique BMX CPU
Address: \\?\usb#vid_80ee&pid_cafe#5&1dd5454f&0&1#{00873fdf-cafe-80ee-aa5e-00c04fb1720b}
Current State: Captured

Maybe there missing some warnings or reports.
DenisF
 
Posts: 31
Joined: 16. May 2012, 15:00

Next

Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: Baidu [Spider] and 25 guests