Opened 14 years ago
Last modified 8 years ago
#5587 new defect
USB device is reported as "unknown device" in Windows Guest on Windows Host — at Version 2
| Reported by: | Egon | Owned by: | |
|---|---|---|---|
| Component: | USB | Version: | VirtualBox 3.0.12 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Windows |
Description (last modified by )
The problem appears related to the slash contained in the device serial number. My guess is that the conversion into a # brokens the guest address.
Using "VBoxManage.exe list usbhost":
UUID: d398cf2d-92ee-44bc-aa8e-6ccef37494eb[[BR]]
VendorId: 0x1781 (1781)[[BR]]
ProductId: 0x0c63 (0C63)[[BR]]
Revision: 2.0 (0200)[[BR]]
Manufacturer: B.Sauter[[BR]]
Product: OpenOCD Debugger[[BR]]
SerialNumber: '''GNU/GPL2'''[[BR]]
Address: {eb781aaf-9c70-4523-a5df-642a87eca567}\0000[[BR]]
Current State: Busy
is reported at the guest as:
UUID: fd66cabb-4b08-4a90-a877-468e438c50b4[[BR]]
VendorId: 0x1781 (1781)[[BR]]
ProductId: 0x0c63 (0C63)[[BR]]
Revision: 2.0 (0200)[[BR]]
Manufacturer: B.Sauter[[BR]]
Product: OpenOCD Debugger[[BR]]
SerialNumber: GNU/GPL2[[BR]]
Address: \?\usb#vid_80ee&pid_cafe'''#gnu#gpl2#'''{00873fdf-cafe-80ee-aa5e-00c04fb1720b}[[BR]]
Current State: Captured[[BR]]
The guest os see the device as "unknown device" with PID and VID to 0.
Change History (2)
comment:1 by , 14 years ago
comment:2 by , 8 years ago
| Description: | modified (diff) |
|---|
Note:
See TracTickets
for help on using tickets.
Tried reflashing the device with a different serial number (with a - instead of /) and obtained a regular Address (\?\usb#vid_80ee&pid_cafe#gnu-gpl2#...). Anyway the device is still "unknown" in guest OS.
The device driver in host system is usblib0 (usblib windows port).