VirtualBox

Ticket #14275 (awaitsfeedback defect)

Opened 6 years ago

Last modified 7 months ago

Error with USB 3.0 devices on VirtualBox 5.0

Reported by: Xopxe Owned by:
Component: guest additions Version: VirtualBox 5.0.0
Keywords: USB Cc:
Guest type: all Host type: Windows

Description

When I try to attach a device (USB 3.0) I got this message:

VirtualBox Error Failed to attach the USB device Ralink 802.11 n WAN [0101] to the virtual machine ... Details USB device 'Ralink 802.11 n WLAN' with UUID ... 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}

Then I try changing to USB 2.0, but the error continue.

My HOST is DELL Inspiron 17r i7 with OS Windows 8.1 64 bits with 16 GB RAM, 1 TB HD (400 GB free).

I got the same error using with Existents VMs, one OS Win XP SP3 and the second with Debian.

Attachments

VBox.log Download (103.8 KB) - added by bigrich99 5 years ago.
Virtual Box log file

Change History

comment:1 Changed 5 years ago by membry

I have also had this issue with all USB devices on my ASUS Z97 4790k rig since I built it in August of 2015. In every iteration of Virtualbox from 5.0 forward, this issue is present for me. I am running a fully patched copy of Windows 10 Enterprise on the host with all the latest hardware drivers from ASUS installed as well. I do not have this issue on my older X58 920 i7 rig running the same version of virtualbox on Linux Mint 17.2, nor was it ever an issue when that was my dedicated Windows system.

For me, this occurs with all USB devices connected to any available 2.0 or 3.0 port.

Below is an example of the error I'm taking, in this case with a 2.0 Flash Drive:

USB device 'UFD 2.0 Silicon-Power32G'
with UUID {b461c516-661d-488a-a102-6a86c29c4e5f}
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}

INFO ON AFFECTED HOST:

Windows 10 Enterprise
Version 10.0.10240 Build 10240
ASUS Z9Z Deluxe 3.1 Motherboard
Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
BIOS Version/Date: American Megatrends Inc. 2501, 6/23/2015
Total Physical Memory 15.9 GB
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

Last edited 5 years ago by membry (previous) (diff)

Changed 5 years ago by bigrich99

Virtual Box log file

comment:2 Changed 5 years ago by bigrich99

Hi
I believe I'm seeing the same problem and only with Windows 10 (x64) host. It works fine on Windows 7.
I use my old Canon scanner which only has 32 bit drivers in a VM so need to capture the USB 2.0 scanner on the VM. First attempt to capture the port nothing happens (does not appear in the device list on the VM). Second attempt to capture the port I get:
Failed to attach the USB device Canon, Inc. CanoScan LiDE 80 [0302] to the virtual machine XP.
USB device 'Canon, Inc. CanoScan LiDE 80' with UUID {816d3751-213e-46af-a1ea-411822c50bdb} 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}

I've tried it with Windows 10 and Windows XP guests and latest Vbox build 5.0.11r104228
The exact same setup works fine with Windows 7 host but stops working when upgraded to Windows 10. VMWare player is still able to share the scanner USB with the same guest OS's so the hardware and host operating system are clearly ok but there's something in Vbox not talking to Windows 10 correctly and gets into some kind of deadlock or race condition when it tries to capture the USB port. Log is attached although I can't see anything significant there.

Please could somebody fix this? Please message if you need any other info/debugging/testing etc.
Thanks
Rich

comment:3 Changed 7 months ago by kcychien

I can confirm this same 'Failed to attach the USB device' bug for my USB device 'UFD 3.0 Silicon-Power32G' happening on the newest virtualbox version 6.1.12 r139181 on my win10 host. This ticket is last modified 5 years ago, perhaps oracle is committed to not fixing this usability issue for users for 5 years straight.

comment:4 Changed 7 months ago by aeichner

  • Status changed from new to awaitsfeedback

This has nothing to do with not being committed to fixing things but this bug tracker is run on a best effort bases and paying customers have a higher priority naturally. If you have a support contract you should contact your Oracle representative to get this issue forwarded. Apart from that you should at least attach a VBox.log and maybe even a VBoxSVC.log and tell exactly what kind of device you are trying to pass through. Your issue might be different from the one reported 5 years ago even though it shows the same symptoms.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use