VirtualBox

Ticket #3895: USBlist.txt

File USBlist.txt, 4.7 KB (added by Perry G, 15 years ago)

Requested USBlist 05-18-2009

Line 
1NOTE: I can not run these commands while the VBox program is running, I get:
2
3F:\.VirtualBox>VBoxManage list usbhost
4VirtualBox Command Line Management Interface Version 2.2.2
5(C) 2005-2009 Sun Microsystems, Inc.
6All rights reserved.
7
8ERROR: failed to create the VirtualBox object!
9ERROR: Could not lock the settings file 'C:\Users\Perry\.VirtualBox\VirtualBox.x
10ml' (VERR_SHARING_VIOLATION)
11Details: code E_FAIL (0x80004005), component VirtualBox, interface IVirtualBox,
12callee <NULL>
13
14
15
16F:\.VirtualBox>
17State before trying to capture USB device and after a HOST reboot:
18
19F:\.VirtualBox>VBoxManage list usbhost
20VirtualBox Command Line Management Interface Version 2.2.2
21(C) 2005-2009 Sun Microsystems, Inc.
22All rights reserved.
23
24Host USB Devices:
25
26UUID: c67f261b-c6ee-4c75-b013-5e503fb6e82e
27VendorId: 0x03f0 (03F0)
28ProductId: 0x5d11 (5D11)
29Revision: 1.0 (0100)
30Manufacturer: HP
31Product: Photosmart C5200 series
32SerialNumber: MY758BF1BT04XQ
33Address: {36fc9e60-c465-11cf-8056-444553540000}\0010
34Current State: Busy
35
36UUID: fe80044d-aaed-4bd3-8441-ff7669e38735
37VendorId: 0x06a3 (06A3)
38ProductId: 0x8021 (8021)
39Revision: 1.16 (0116)
40Manufacturer: Chicony
41Product: Saitek Eclipse II Keyboard
42Address: {36fc9e60-c465-11cf-8056-444553540000}\0024
43Current State: Busy
44
45UUID: f258dcc3-b93a-45ad-8197-bc46eab37a99
46VendorId: 0x0951 (0951)
47ProductId: 0x1603 (1603)
48Revision: 2.0 (0200)
49Manufacturer: Kingston
50Product: DataTraveler 2.0
51SerialNumber: 001D0F0CAAA3SK880A0D014B
52Address: {36fc9e60-c465-11cf-8056-444553540000}\0022
53Current State: Busy
54
55
56F:\.VirtualBox>
57
58State after trying to select USB device Win-XP guest no filters and clicking on the device in the guest device menu. Additionally this caused the VBoxsvc to crash (see Windows report below this!
59
60
61F:\.VirtualBox>VBoxManage list usbhost
62VirtualBox Command Line Management Interface Version 2.2.2
63(C) 2005-2009 Sun Microsystems, Inc.
64All rights reserved.
65
66Host USB Devices:
67
68UUID: f35e06e8-79f4-4827-9cbe-3c29bf1b6446
69VendorId: 0x03f0 (03F0)
70ProductId: 0x5d11 (5D11)
71Revision: 1.0 (0100)
72Manufacturer: HP
73Product: Photosmart C5200 series
74SerialNumber: MY758BF1BT04XQ
75Address: {36fc9e60-c465-11cf-8056-444553540000}\0010
76Current State: Busy
77
78UUID: 0a3cf64f-2a2b-42ac-8d41-d47ae53ed8ba
79VendorId: 0x06a3 (06A3)
80ProductId: 0x8021 (8021)
81Revision: 1.16 (0116)
82Manufacturer: Chicony
83Product: Saitek Eclipse II Keyboard
84Address: {36fc9e60-c465-11cf-8056-444553540000}\0024
85Current State: Busy
86
87UUID: 7b73a47b-47d9-4459-a60a-15fd9d6f41c7
88VendorId: 0x0951 (0951)
89ProductId: 0x1603 (1603)
90Revision: 2.0 (0200)
91Manufacturer: Kingston
92Product: DataTraveler 2.0
93SerialNumber: 001D0F0CAAA3SK880A0D014B
94Address: {36fc9e60-c465-11cf-8056-444553540000}\0021
95Current State: Busy
96
97
98F:\.VirtualBox>
99
100NOTE: While the device DataTraveler 2.0 shows in this list it is no longer available to Windows. It simply shows as non-existant in explorer or safely remove USB hardware. To bring this back I must unplug it and plug it back in (sometimes several times). Then Windows gets that it is available and loads the device.
101
102Windows problem report of crash:
103
104Problem signature
105Problem Event Name: APPCRASH
106Application Name: VBoxSVC.exe
107Application Version: 2.2.2.0
108Application Timestamp: 49f5fbf7
109Fault Module Name: VBoxDDU.dll
110Fault Module Version: 0.0.0.0
111Fault Module Timestamp: 49f5fa48
112Exception Code: c0000005
113Exception Offset: 00019434
114OS Version: 6.0.6001.2.1.0.256.6
115Locale ID: 1033
116Additional Information 1: f3b8
117Additional Information 2: 35c310a4ca337ca27efb63ede506985e
118Additional Information 3: 9fe5
119Additional Information 4: 5d209e3173825e38ae96dfc30034002f
120
121
122After this I can then open the guest and unplug and plug in to get focus but not until after the VBox USB driver has been loaded in Windows and crashes VBox. Bringing VBox up after the USB device driver has been loaded allows me to use the USB device as it should be untill I reboot the host and of course Windows unloads the VBox USB device driver.
123
124I really think it has something to do with the VBox USB device driver not being loaded in Windows at system reboot. When VBox tries to load it at the same time that it is requiring Windows to install the driver it causes it to crash.
125

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy