#11251 closed defect (obsolete)
USB not working at all (all devices are busy)
| Reported by: | Karagul | Owned by: | |
|---|---|---|---|
| Component: | USB | Version: | VirtualBox 4.2.4 |
| Keywords: | Cc: | ||
| Guest type: | all | Host type: | Windows |
Description
USB devices in drop-down list are ALL in "busy" state. If I try to attach one (a USB 232 converter in this example) I get the following error:
Failed to attach the USB device Prolific Technology Inc. USB-Serial Controller [0300] to the virtual machine WinXP Devel.
USB device 'Prolific Technology Inc. USB-Serial Controller' with UUID {1e04c48b-fcb2-4509-bfba-8ea06084b6be} is busy with a previous request. Please try again later.
Result Code: E_INVALIDARG (0x80070057)
Component: HostUSBDevice
Interface: IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee: IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}
Sometimes, instead, the device becomes "captured" but nothing happens (device is NOT attached) and retrying to attach it yields the same error as above.
This does NOT seem to happen on linux host. Log is attached.
Attachments (3)
Change History (31)
by , 12 years ago
| Attachment: | vboxlog.txt added |
|---|
by , 12 years ago
| Attachment: | VBox.log.1 added |
|---|
comment:2 by , 12 years ago
Similar problem with Macbook pro running Mac Os 10.8.2 and VB 426 with windows 7 or windows 8 on the top of it. Any USb device is not launched and a driver problem is reported. Really a big problem for me,
comment:3 by , 12 years ago
The same issue in VirtualBox-4.2.10-84105-Win, Host - Windows 8 Single Language 6.2.9200.16496 (Win8 RTM), Guest OS is any of: winxpsp3 prof ru (ver.5.1.2600)/win7 x32 prof ru(ver.6.1.7600). Any USB device is busy "with a previous request". Please send any information on the solution of this problem.
comment:4 by , 12 years ago
I believe this is the USB 3.0 host only bug described here: https://www.virtualbox.org/ticket/8873
comment:5 by , 11 years ago
USB function has broken again since 4.2.18 (include), all 4.3 releases doesn't work on some Windows 7 64bit machines. See thread:
https://forums.virtualbox.org/viewtopic.php?f=6&t=57946&p=279205#p279205
comment:7 by , 10 years ago
Not being able to pass through USB devices to guest VM's due to 'device is busy' error has been around for quite some time now. It still seems evident in version 4.3.12.
Nearly 2 years and no resolution to the issue. Since no correspondence from development I would suggest a workaround: use another product.
comment:8 by , 10 years ago
I think this is right context and set of symptoms to match my own experience. Host is WIndows 7 x86_64, Guest is Fedora 20. VB 4.3.x won't mount my HTC phone via USB, complaining of being busy. Reverting to 4.2.16 ~Resolves The Problem~. However, my kernel is then too recent for 4.2.16 so that version of VB doesn't want to support shared folders. Rather than downgrade the kernel I un-reverted (?) to the most recent VB 4.3. Once again, no USB.
Is there anything I might submit that would be of help? It seems to me that I've got a "critical case" potentially useful to root cause analysis.
BTW, my USB is 2.x, not 3.x. At the moment, I'm plugged into a slow 2.x port and Windows is trying to teach me to do otherwise.
comment:9 by , 10 years ago
I have this problem also. Win7 64bit,asus m4a87td evo. 22 months ongoing and official word is it's working fine for us. looks like 4.2.16 is where i stay.
comment:10 by , 10 years ago
Hi wbmccarty and boochip,
A workaround to this issue is to use the latest VB, for example, 4.3.16, with 4.2.16 USB Windows drivers, see thread:
https://forums.virtualbox.org/viewtopic.php?f=6&t=57946&p=279205#p279205
Cheers,
comment:11 by , 9 years ago
Ticket 14287 and this ticket 11251 look similar. Solution from https://forums.virtualbox.org/viewtopic.php?f=6&t=39104 also worked for me for VB 5.0.14. Except it's not explained what exactly it does, and whose bug is it.
comment:12 by , 9 years ago
The problem is still persistent. Also in the newest version (5.0.14). This issue is very evil for many people and needs to be fixed as soon as possible. :/
The solution in the prepost is not working!
Debug infos like screenshots and logfiles can be found at my post here: https://forums.virtualbox.org/viewtopic.php?f=6&t=75909
comment:13 by , 8 years ago
The same issue still exists in 5.0.20 , Host is Windows 7 64 bit , guest is Ubuntu 14.0.4LTS 4.2.0.36 kernel Prolific USB to Serial :0300 work around is with USB filter for the Prolific but when you have more than one Prolific cable and you want to use one on the host and one the Guest is a bit more tricky when plugin and unplug the cables
comment:14 by , 8 years ago
The same issue also exists in 5.0.20 on Windows 7 Professional (Host) with guest Windows 7 Professional with all PEAK PCAN USB dongles und KEIL ulink (1/2 and ME) adapters.
When a filter for the adapter is applied, the device can indeed be used in the VM, but disconnect or connect of a device is in operation of the VM impossible. If you try this, the device in both systems blocks.
comment:15 by , 8 years ago
Additional Informations: (disconnect Peak Adapter via usb device Manager and try to capture it after one minute again). In both systems the Adapter is not available anymore, up to this moment then i'm closing the VM.
Message of the error box:
Das USB-Gerät PEAK System VER1:PEAK VER2:02.8.01 DAT :06.05.2004TIME:09:35:37 ... [1CF0] konnte nicht an die virtuelle Maschine Test gebunden werden.
USB device 'PEAK System VER1:PEAK VER2:02.8.01 DAT :06.05.2004TIME:09:35:37 ...' with UUID {6f38ecc7-3b11-4b7b-8391-c957b93429e4} is busy with a previous request. Please try again later.
Fehlercode:E_INVALIDARG (0x80070057) Komponente:HostUSBDeviceWrap Interface:IHostUSBDevice {c19073dd-cc7b-431b-98b2-951fda8eab89} Callee:IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
comment:16 by , 8 years ago
More informations (vboxmanage list usbhost): the recaptured device is now in state HELD.
UUID: 4d09421f-51e5-4a03-8707-8589644bf5c9
VendorId: 0x0c72 (0C72)
ProductId: 0x000c (000C)
Revision: 28.1 (2801)
Port: 0
USB version/speed: 1/Full
Manufacturer: PEAK System
Product: VER1:PEAK VER2:02.8.01 DAT :06.05.2004TIME:09:35:37
Address: \\?\usb#vid_80ee&pid_cafe#7&25b9522b&0&2#{00873fdf-cafe-80ee-aa5e-00c04fb1720b}
Current State: Captured
UUID: 6f38ecc7-3b11-4b7b-8391-c957b93429e4
VendorId: 0x0c72 (0C72)
ProductId: 0x000c (000C)
Revision: 28.240 (28240)
Port: 0
USB version/speed: 1/Full
Manufacturer: PEAK System
Product: VER1:PEAK VER2:02.8.01 DAT :06.05.2004TIME:09:35:37
Address: \\?\usb#vid_80ee&pid_cafe#7&25b9522b&0&3#{00873fdf-cafe-80ee-aa5e-00c04fb1720b}
Current State: Held
comment:17 by , 8 years ago
I am surprised no one has mentioned this. I found a solution when googling that fixed my problem. (All USB devices busy in all of my virtual computers)
Using regedit go to the following registry entry and delete the "UpperFilters" key. Reboot the host computer.
"HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Class > {36FC9E60-C465-11CF-8056-444553540000}"
I have seen a similar problem with my DVD player in the past. An "UpperFilters" key would disable the drive. It appears that they can't be trusted :)
comment:18 by , 8 years ago
Thank you sgraves!! I have been searching on here for a day and a half, and your mention of the UpperFilters key issue was the first I had seen anywhere....it fixed my problem of an XP SP2 guest on a Win 7 Pro host always having USB device status of "Busy"...
comment:19 by , 8 years ago
I still have this issue. I have tried the solution specified here and others. I have not been able to get any USB device forwarded from my Windows 10 host to my Arch linux guest.
As described above, I am able to get a device into the "captured" state which prevents Windows from accessing the device but it never appears in the guest. Trying to "reattach" the device by selecting it again via the USB menu results in the busy error described.
Using a filter instead means the device is always "captured" but I am unable to detect it in the guest.
I've tried the following to resolve this issue, all with no success;
- A few different ports of both USB3.0 and USB2.0.
- USB2.0 and USB3.0 settings on the machine settings.
- Manually installing VirtualboxUSB driver
- Deleting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}\UpperFilters as described here and on this bug.
- Alternative devices (other USB sticks and keyboards).
- More permissive USB filters.
- Disabling device in "Device Manager" before attempting to attach in VirtualBox.
- Plugging in USB device in at different times; before starting virtualbox, before starting vm, after starting vm.
Please let me know if there's anything else I can attempt to help debug this issue.
Cheers
Host OS: 64-bit Microsoft Windows 10 Professional Build 10586
Host Hardware: Intel Core i7-5820K, ASUS SABERTOOTH X99 (full hardware report here)
Virtualbox version: Version 5.0.26 r108824 (although the bug has been present since I started using Virtualbox on Windows 10 in approx. November 2015)
x86_64 GNU/Linux
Virtualbox Extensions:
C:\Program Files\Oracle\VirtualBox>vboxmanage list extpacks Extension Packs: 1 Pack no. 0: Oracle VM VirtualBox Extension Pack Version: 5.0.26 Revision: 108824 Edition: Description: USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk Encryption. VRDE Module: VBoxVRDP Usable: true Why unusable:
Guest: Arch Linux - Linux morty 4.6.4-1-ARCH #1 SMP PREEMPT Mon Jul 11 19:12:32 CEST 2016
Guest Addon Packages: Arch supported packages; virtualbox-guest-utils virtualbox-guest-dkms 5.1.2-2
VM Info:
C:\Program Files\Oracle\VirtualBox>vboxmanage showvminfo "Morty" --details
Name: Morty
Groups: /
Guest OS: Arch Linux (64-bit)
UUID: aa708e8d-9eaf-4ba7-839e-ceebd013782d
Config file: C:\Users\chris\VirtualBox VMs\Morty\Morty.vbox
Snapshot folder: C:\Users\chris\VirtualBox VMs\Morty\Snapshots
Log folder: C:\Users\chris\VirtualBox VMs\Morty\Logs
Hardware UUID: aa708e8d-9eaf-4ba7-839e-ceebd013782d
Memory size: 12869MB
Page Fusion: off
VRAM size: 128MB
CPU exec cap: 100%
HPET: off
Chipset: piix3
Firmware: BIOS
Number of CPUs: 6
PAE: off
Long Mode: on
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: on
IOAPIC: on
Time offset: 0ms
RTC: UTC
Hardw. virt.ext: on
Nested Paging: on
Large Pages: on
VT-x VPID: on
VT-x unr. exec.: on
Paravirt. Provider: Default
State: running (since 2016-08-15T09:31:13.687000000)
Monitor count: 2
3D Acceleration: on
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Default Frontend:
Storage Controller Name (0): IDE
Storage Controller Type (0): PIIX4
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): 3
Storage Controller Bootable (1): on
IDE (1, 0): C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso (UUID: 1118fffd-083f-49ea-8840-b38c806d57a4)
SATA (0, 0): C:\Users\chris\VirtualBox VMs\Morty\Snapshots/{a2de49f2-ff42-48a0-8a49-88341856f450}.vdi (UUID: a2de49f2-ff42-48a0-8a49-88341856f450)
SATA (2, 0): D:\VirtualBox Disks\MORT-HDD.vdi (UUID: 119a6859-83e5-49e2-a202-c9cc0fb7d441)
NIC 1: MAC: 080027F15A26, Attachment: Bridged Interface 'Intel(R) Ethernet Connection (2) I218-V', 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: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1: disabled
UART 2: disabled
UART 3: disabled
UART 4: disabled
LPT 1: disabled
LPT 2: disabled
Audio: enabled (Driver: DSOUND, Controller: AC97, Codec: AD1980)
Clipboard Mode: Bidirectional
Drag and drop Mode: Bidirectional
Session name: GUI/Qt
Video mode: 2560x1335x32 at 0,0 enabled
VRDE: disabled
USB: enabled
EHCI: enabled
XHCI: disabled
USB Device Filters:
<none>
Available remote USB devices:
<none>
Currently Attached USB Devices:
<none>
Bandwidth groups: <none>
Shared folders:
Name: 'C_DRIVE', Host path: 'C:\' (machine mapping), writable
Name: 'D_DRIVE', Host path: 'D:\' (machine mapping), writable
VRDE Connection: not active
Clients so far: 0
Video capturing: not active
Capture screens: 0
Capture file: C:\Users\chris\VirtualBox VMs\Morty\Morty.webm
Capture dimensions: 1024x768
Capture rate: 512 kbps
Capture FPS: 25
Guest:
Configured memory balloon size: 0 MB
OS type: Linux26_64
Additions run level: 2
Additions version: 5.1.2_OSE r108956
Guest Facilities:
Facility "VirtualBox Base Driver": active/running (last update: 2016/08/15 09:31:50 UTC)
Facility "VirtualBox System Service": active/running (last update: 2016/08/15 09:31:53 UTC)
Facility "Seamless Mode": active/running (last update: 2016/08/15 09:31:50 UTC)
Facility "Graphics Mode": active/running (last update: 2016/08/15 09:31:50 UTC)
Snapshots:
Name: All working (UUID: 45a2fef9-3bf1-4952-ad83-07c942dc57ef)
Name: Recently unborked (UUID: 381f6672-4c00-4f63-8275-e9681874afad) *
Logs
VBox.log after attempting to attach
list usbhost
C:\Program Files\Oracle\VirtualBox>vboxmanage list usbhost
Host USB Devices:
UUID: 67f31219-92e7-4878-829f-502dde5f6824
VendorId: 0x0000 (0000)
ProductId: 0x0000 (0000)
Revision: 0.0 (0000)
Port: 0
USB version/speed: 0/Full
Current State: Available
UUID: bd0e5ca6-fc90-42a6-b9f8-9e7caadb13ce
VendorId: 0x0426 (0426)
ProductId: 0x3011 (3011)
Revision: 1.0 (0100)
Port: 0
USB version/speed: 1/Full
Manufacturer: MKEYBOARD
Address: {36fc9e60-c465-11cf-8056-444553540000}\0034
Current State: Busy
UUID: 4058f0c3-a9a7-4cea-bcb8-6b4c48486430
VendorId: 0x046d (046D)
ProductId: 0x081b (081B)
Revision: 0.16 (0016)
Port: 0
USB version/speed: 2/High
Manufacturer: Logitech, Inc.
Product: Webcam C310
SerialNumber: 431020A0
Address: {36fc9e60-c465-11cf-8056-444553540000}\0017
Current State: Busy
UUID: 4e957cf0-ab98-4bd8-ab1a-d252f5b18d89
VendorId: 0x0781 (0781)
ProductId: 0x5588 (5588)
Revision: 0.16 (0016)
Port: 0
USB version/speed: 2/High
Manufacturer: SanDisk
Product: ExtremePro
SerialNumber: AA011128151931240896
Address: {36fc9e60-c465-11cf-8056-444553540000}\0083
Current State: Captured
UUID: 3a7c138f-3888-45ce-bb8a-d823851efeab
VendorId: 0x172f (172F)
ProductId: 0x0037 (0037)
Revision: 1.7 (0107)
Port: 0
USB version/speed: 1/Full
Manufacturer: WALTOP
Product: Graphics Tablet
Address: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0122
Current State: Busy
UUID: 90e6d731-b127-4f57-9d0d-19ef1f0a84df
VendorId: 0x1e7d (1E7D)
ProductId: 0x3750 (3750)
Revision: 0.16 (0016)
Port: 0
USB version/speed: 1/Full
Manufacturer: ROCCAT
Product: KAVE XTD Headset
Address: {36fc9e60-c465-11cf-8056-444553540000}\0104
Current State: Busy
UUID: 15f106a1-80c3-4cb3-a97f-7e429fb3ebba
VendorId: 0x28de (28DE)
ProductId: 0x1142 (1142)
Revision: 0.1 (0001)
Port: 0
USB version/speed: 2/High
Manufacturer: Valve Software
Product: Steam Controller
Address: {36fc9e60-c465-11cf-8056-444553540000}\0082
Current State: Busy
UUID: 58332c46-818a-47f4-a37e-f3e7c17be5ac
VendorId: 0xe0ff (E0FF)
ProductId: 0x0002 (0002)
Revision: 0.1 (0001)
Port: 0
USB version/speed: 1/Full
Manufacturer: A.....
Product: Shogun Bros. Ballista MK-I Mouse
Address: {36fc9e60-c465-11cf-8056-444553540000}\0047
Current State: Busy
Error on attempting to "reattach" usb device
Failed to attach the USB device SanDisk ExtremePro [0010] to the virtual machine Morty.
USB device 'SanDisk ExtremePro' with UUID {4e957cf0-ab98-4bd8-ab1a-d252f5b18d89} is busy with a previous request. Please try again later.
Result Code: E_INVALIDARG (0x80070057)
Component: HostUSBDeviceWrap
Interface: IHostUSBDevice {c19073dd-cc7b-431b-98b2-951fda8eab89}
Callee: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
comment:20 by , 8 years ago
So interestingly today I installed a new standalone USB3.0 card and attempted the same thing and everything worked as expected on the ports connected to that new card.
So this issue only affects the USB3.0 devices connected to the Asus Mobo. Everything else works fine on the Asus ports afaik, so this only seems to be an issue when these ports are used with Virtualbox.
follow-ups: 23 24 comment:21 by , 8 years ago
Figured out why my Virtualbox VM's were all saying USB devices were all busy. Last week I installed a new version of Wire shark that comes with USBPcap. Turns out Virtualbox and USBpcap don't like each other very much...
Uninstalled USBPcap and my USB pass through on my VM's all started working again.
comment:23 by , 8 years ago
Replying to VLNinja70:
Figured out why my Virtualbox VM's were all saying USB devices were all busy. Last week I installed a new version of Wire shark that comes with USBPcap. Turns out Virtualbox and USBpcap don't like each other very much...
Uninstalled USBPcap and my USB pass through on my VM's all started working again.
VLNinja, you are a genius. This fixed my problem to, uninstalled usbPcap, rebooted and all is well. I wonder if the wonderful folks over at VBox/Oracle could put a check in for this and report it to the user, or at least put it in an FAQ somewhere as something to try if there are USB problems.
comment:24 by , 8 years ago
Replying to VLNinja70:
Figured out why my Virtualbox VM's were all saying USB devices were all busy. Last week I installed a new version of Wire shark that comes with USBPcap. Turns out Virtualbox and USBpcap don't like each other very much...
Uninstalled USBPcap and my USB pass through on my VM's all started working again.
Cannot thank you enough, was really loosing hope here. Uninstalled USBPcap et voilà, USB on VM working again!
comment:25 by , 7 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
There is another ticket (#16032) for the USBcap issue so I'll close this one.
comment:26 by , 7 years ago
I wrote up a complete guide to working around this here: https://www.zachpfeffer.com/single-post/A-fix-for-a-USB-drive-or-any-USB-device-not-working-in-VirtualBox.
comment:27 by , 7 years ago
@Zach Pfeffer
You've already commented in ticket #16032, where this ticket points to. There's no need to post to every ticket with your blog post, unless you are trying to promote it... ;)
comment:28 by , 7 years ago
Hey socratis. Just trying to get the word out since people enter from different search vectors. You're welcome to nuke my post or redirect. Just happy to help. :)
I have the same issue with USB in virtualbox 4.2.6, host OS is Windows 8 64, guest OS is Windows XP Pro 32 bit. Trying to attach any USB device does not bring any visible results, and futher efforts to do this cause an error message telling that device is busy, for example: "USB device 'JetFlash Mass Storage Device' with UUID {0bfa92ef-936c-4558-ab6a-5e04b2bf3777} is busy with a previous request. Please try again later." I have got this problem only on Windows 8 host, I have never seen it in other host OS, such as Windows XP, Windows 7, Ubuntu 12.04, Ubuntu 12.10. Log is attached as "Vbox.log.1". Waiting with hope for solution of this problem.