Failed to create a proxy device for the USB device

[Dieter Fauth]

I had similar problems already with older versions. Is there a way to debug it down to the root? The vbox filter driver seams to be installed. I have two devices mapped to the guest. Usually both don't work after seeing this error.

When I unplug the device (Siemens phone sx353), it finally works. (Guest == WinXP SP2)

With an Ubuntu Guest I saw a similar message for a different device (Barcode reader == CDC-ACM). unplug/replug helps sometimes.

This was for an RNDIS device (PDA phone XDA Diamond with Win Mobile 6.1): Failed to create a proxy device for the USB device. (Error: VERR_IO_GEN_FAILURE).

Result Code: E_FAIL (0x80004005) Component: Console Interface: IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}

Quite often the vboy server process crashes after I plug in the device. The log files did not contain usefull info, but perhaps I can rise the log levels?

Since I live closeby to Endersbach, I would even visit you with the phone to demonstrate.

[Dieter Fauth]

More details: I did close The vbox gui (and all guests). Later I reopened and started a vm. No USB devices available, Then with Devices/Usb I tried to add the SX353 and got this error: Failed to attach the USB device ... to the vm.

USB device 'Siemens AG Gigaset SX 353 ISDN' with UUID {f68e8bc5-4d4e-4197-867c-d09ba3ac867a} 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 {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}

It could be a secondary error, but I recall seeing it right after a reboot of the host. Then I tried to attach the HTC phone (RNDIS), and got the error for the SX353 again. Is that to be expected here?

[Dieter Fauth]

Problem still exists in 2.04, though the Siemens phone works most of the time now. The HTC (ActiveSync) never works and usually causes the VboxSrv to crash when I plug the phone in. I succest looking in the order of loaded drivers, perhaps the MS ActiveSync has some other registry entries that prevent your driver from working properly. If you need help in debugging with the device, let me know. I live in Schorndorf.

[Richard]

Still broken in VirtualBox version 2.0.6 Host = MACOSX Guest windows XP or Ubunutu Linux 8.10 The guest has USB 2.0 (EHCI) Controller enabled.

I have tried enabling a filter and removing the filter for the Toshiba 2 GB Pen Drive. The behaviour of vbox is roughly the same.

Before I attempt to insert my Toshiba pen drive, there is a USB list of my USB devices (some greyed out).

• iSight connects if I click on it; it even shows up in Windows Explorer.
• IR receiver connects if I click on it; I did not investigate this any further.
• USB Bluetooth Host Controller, when clicked on, reports that it is "in use by someone else".
  

I plugged in my Toshiba pen drive 2 times and had 2 different outcomes:
(1) My vbox USB list suddenly becomes nil.
(2) My entire Mac froze up. After unplugging the Toshiba pen drive and waiting about 10 seconds, the Mac returned to normal.

Windows, of course, never sees the pen drive. BTW, my Seagate USB HDD has never been usable by vbox. Both of those devices work fine in normal mode on MACOSX, Linux, and Windows in their native modes.

My observation is that USB and Bluetooth are just unstable in vbox 2.0.6.

[fuzi]

More info : Using V2.2.2r46594 (Vista Business 32 bit host) to run a Debian (Etch) client.

VM running fine, plugged in a Seagate Freeagent Go external HDD and got a virtualbox error:

Failed to attach the USB device '''Unknown device 0C24:000F[1915]''' to the ......
Failed to create a proxy device for the USB device.

Result Code: E_FAIL (0x80004005)
Component:   Console
Interface:   IConsole {9511bc54-15ee-4ddf-808e-472aba03809c}

Doesn't kill the VM however, and it's repeatable (clear error, unplug, replug device).

No change regardless of USB2.0 enabled or otherwise.

Sounds awfully a lot like ticket #1655 as well, particularly down to me also having an issue with a piece of seagate kit. Experimenting with booting the VM (or virtualbox gui for that matter) with the offending device plugged in doesn't cause any issues mind you, so might not be the same thing.

[fuzi]

Quick update, have just installed 3.0.0r49315, using the same VM and the error no longer appears, i'm now able to mount the device.

Aside from the upgrade to Virtualbox, the only change was that the external HDD has been reformatted (i'm pretty sure it was formatted as HFS+ from memory) to NTFS.

[Frank Mehnert]

So we will close this ticket. Please reopen if the problem reappears for someone else.

[ile]

Hi,

I'm trying to use this Bluetooth USB dongle, it works in native Win7 but not in Virtualbox.

Virtualbox host = Win7 x64 Virtualbox guest = Win XP 32bit

See attached screenshot for more information.

Am I in the right place (ticket)?

[ile]

Forgot to add that I use the latest Virtualox version, 3.1.4 r57640.

[ile]

Same problem in 3.1.6.

[deelay]

Still broken in 3.2.0.

[willsola]

Error

[willsola]

I got a similar error attaching an Ipaq H3835 (with windows pocket pc 2002) to the VirtualBox. Host: windows 7, Guest: Windows XP SP 3. I already attached the log file and the error image (VBerrorVerrIoGenFailure.png)

[ile]

Still broken, 3.2.6. Attached image.

[willsola]

Fixed in 3.2.6 for the Ipaq H3835

[ile]

The device I'm having problems with is this, btw: ​http://www.dealextreme.com/details.dx/sku.11866

[ile]

Now it works, thank you! In 3.2.8

[Frank Mehnert]

So I will close this ticket. Please reopen if necessary (but make sure you test VBox 3.2.8 first).

[Alexey Korepov]

Problem with Amicon VPN still exist for me on Debian Lenny as host, Windows XP as Guest, Virtualbox version 3.2.8-64453~Debian~lenny

In logs I see the error: 00:06:33.120 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={6375231a-c17c-464b-92cb-ae9e128d71c3} aComponent={Console} aText={Failed to create a proxy device for the USB device. (Error: VERR_READ_ERROR)} aWarning=false, preserve=false

lsusb: Bus 003 Device 002: ID a420:5420