USB 2.0 aka EHCI does not work

[nino.dago]

Hi all!
I have the same problem on last release of VirtualBox. In other words, sometimes the host (WinXP SP2) has a VBox crash, and the error is this (translating from Italian, sorry for non-precision ) :
Application which crashed: vboxsvc.exe, version 1.0.0.1;
Module which crashed: vboxddu.dll, version 0.0.0.0
error address: 0x00015372.

Every time I have this crash, my VBox doesn't stop, it appears still running and I can close and restart (the virtual has also WinXP SP2).

Examining the Event Viewer of WinXP, it seems that around the time of crash the system is going to start or it starts a service, and exactly the following ones:
- HD Read Error;
- Service Connection Manager for Remote Access about to start (many times it happened).
- Messenger Sharing Folders USN Journal Reader about to start.
I don't know if these services or these events could interfere in some way with VBox, but the problem is that every time I have the crash, the only thing I can do to reenable USB peripherals is to reboot host. I think in some way vboxddu.dll, which crashes, still mantains in memory call to usb peripherals, and so even if I reboot the VBox, those memory address are busy. Infact, when I try to connect the usb peripheral the error message in VBox is this:
USB device 'Generic USB2.0-CRW' with UUID {7412e689-ee3f-4c49-94f8-0e44c356f85d} is busy with a previous request. Please try again later.

I tried to give you all details I tried to find, hoping to find a solution. Unfortunately, the tip given by some users which have linux hosts cannot be used in this case because we can't change the source code like them.
Have some WinXP host user found a solution?

Thanks in advance for replies, and sorry for my bad english.

Bye Nino

[war59312]

Yeah so sad, still happens every time in 2.0.4. I have never been able to get a single USB device to work in Virtual Box.

[nino.dago]

Yeah so sad, still happens every time in 2.0.4. I have never been able to get a single USB device to work in Virtual Box.

I found a little workaround to bypass the problem. It seems that, in my case, the problem starts when I extract USB peripheral from computer while VirtualBox is running, while if I attach and extract USB peripheral while VirtualBox is down, I have no problems and it's recognized in VirtualBox if it's mapped in USB peripherals list.

So you should just avoid the plugging in and out while the VirtualBox is on.

I hope to help you.

Bye
Nino

[war59312]

ok, that works but what really stinks is that i cant use my keyboard on my host if i do this..

but i have to do this to use my usb keyboard in the guest.. ouch, pretty lame..

and yes this is with additions correctly installed...

[nino.dago]

ok, that works but what really stinks is that i cant use my keyboard on my host if i do this..

but i have to do this to use my usb keyboard in the guest.. ouch, pretty lame..

and yes this is with additions correctly installed...

I'm not sure to understand... Aren't you able to use keyboard in host while you are using guest? I seem that keyboard is handled differently from other peripherals, I mean that VirtualBox should permit to pass keybord from host to guest just pushing a button and without register keyboard to virtual system.
You should verify this setting.
An alternative is to change usb keyboard to ps/2 keyboard. Do you have ps/2 plug in your pc? If you have, find a converter from usb to ps2 (very cheap) and use ps/2 port to bypass the problem.
Bye
Nino

[war59312]

Right, you'd think so.

Yeah I know about the workaround, just stinks that's required.

[nino.dago]

Sorry, but I can't help you more than what I said before... also because I'm an user just like you!!

I'd like that VBox developers will answer to our questions, but in this thread there's silence...

[anewguy]

I am also having the USB problems running Windows XP Pro SP3 as host, Ubuntu linux 8.10 as guest. Prior to starting virtualbox, a vboxmanage list usbhost shows the device there with a status of busy. I start virtualbox, check the USB filters to be sure the device is there (why a blank filter doesn't work for everything as it's supposed to is another matter), then start the Ubuntu VM. The USB device does not show in a "lsusb". When I place my mouse over the USB icon on the bottom status bar it says no devices attached - but the dang thing is plugged in. Vboxmanage shows the device now as captured. Right clicking the USB icon on the bottom status bar results in the device busy with previous request error box. I have tried EVERYTHING in this thread, as well as things in many, many other threads in other forums, and cannot find a solution for this. I suspect SOMETHING with XP Pro SP3 and the current version of virtualbox. I may tried downloading an older version of virtualbox to see if that helps.

Dave

[TerryE]

Have you set up Ubuntu as per the Forum FAQ?

[anewguy]

I *THOUGHT* I had. I guess I'll do this all one more time. I'll delete the VM, delete virtualbox, then reinstall virtualbox and install Ubuntu (it will be 8.04 since I don't have the 8.10 image). Then I'll follow the FAQ again. I won't add the vm additions, etc., until instructed to do so, and I'll leave out the other libs I need for now (GTK and libusb development libs) and see what I happens. I'll post back later after I've had a chance to do that all again.

Thanks!
Dave

[anewguy]

Okay, I completely removed virtualbox and my vm's. I then downloaded from the virtualbox.org site the peul version 1.6.6 (I've read other places that 1.6.6 worked for their USB when 2.04 didn't).

I defined a Vm as Ubuntu 8.04, created a virtual disk of the default 8 gig size automatically expandable.

I went to settings and to USB, enabled botht USB controllers.

I added a blank filter (says it allows all devices to pass).

I installed Ubuntu 8.04 from an ISO image.

I installed the additions to the Ubuntu guest.

Restarted as requested every place.

On final restart, waited for VM to come up, then plugged in one of my USB flash drives. VM has no indication it exists. The USB icon on the bottom task bar only shows the keyboard and the mouse.

Did a vboxmanage list hostusb - the flash drive doesn't show there at all.

I have done nothing else - none of the suggestions from the many other sites, etc..

The WIKI and FAQ did not indicate anything specific for a Linux GUEST, particularly where USB is concerned.

So, I have a "raw" installation - I didn't let Ubuntu install any new updates, I didn't install the development libraries I require - it's just raw.

So, given that, given Windows XP Pro SP3 as the host OS and Ubuntu Linux 8.04 with the additions as the guest OS, I am ready for more instruction as to how to get this to work.

Dave

I shutdown the VM completely and then using the virtualbox console tried to see if it saw my USB device in settings - it didn't.

Closed out of virtualbox.

vboxmanage list usbhost now showed my flash drive as busy.

Opened virtualbox.

Went to USB settings - did add, my device showed so I clicked on it. A filter was added for it, so I now had 2 filters - the empty one followed by the device-specific one.

vboxmanage list usbhost still showed my flash drive as busy.

Started the Ubuntu guest OS VM. Immediately, vboxmanage list usbhost showed the flash drive as captured.

When Ubuntu was all the way up and I was logged on and sitting on the desktop, the flash drive was not visible. Went to the USB icon on the lower status bar - just putting cursor over it it said no devices attached. Did a right click and selected my device from the list - got the busy error box again:


USB device 'LEXAR JD FIREFLY' with UUID {5690c3e1-8d9e-452d-bc0d-f3c92997f414} 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}


While this error box is up, vboxmanage list usbhost still showed the flash drive as captured.

Closed the error box.

Vboxmanage list usbhost still showed the flash drive as captured.

Ubuntu does not show any USB devices, just the busses, even as super user:

dave@dave-ubuntu-804:~$ sudo lsusb
[sudo] password for dave:
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
dave@dave-ubuntu-804:~$



I don't know what else to try now without someones help. I hope I have provided enough information for someone.

Thanks in advance!
Dave


EDIT#2: Did the following from a website pointed to in the wiki/faq:

USB
To get USB support, you need the PUEL version. Via the GUI, there is an option to enable USB.

Furthermore, your user must be able to access /proc/bus/usb/*

Since Gutsy, /proc/bus/usb is not mounted by default. In Intrepid, you need to add the following lines to /etc/init.d/mountdevsubfs.sh right after domount devpts "" /dev/pts devpts -onoexec,nosuid,gid=$TTYGRP,mode=$TTYMODE but before the ending } for the dostart shell function. For Gutsy and Hardy you just need to edit /etc/init.d/mountdevsubfs.sh and uncomment the following lines:

#
# Magic to make /proc/bus/usb work
#
mkdir -p /dev/bus/usb/.usbfs
domount usbfs "" /dev/bus/usb/.usbfs -obusmode=0700,devmode=0600,listmode=0644
ln -s .usbfs/devices /dev/bus/usb/devices
mount --rbind /dev/bus/usb /proc/bus/usbThen run the script that you just edited:

sudo /etc/init.d/mountdevsubfs.sh startIn order to give users in the vboxusers group write permissions to the devices in /proc/bus/usb, you'll need to edit some rules in /etc/udev/rules.d.

Under Gutsy, edit /etc/udev/rules.d/40-permissions.rules to say the following:

# USB devices (usbfs replacement)
SUBSYSTEM=="usb_device", MODE="0664", GROUP="vboxusers"Under Hardy and Intrepid, edit /etc/udev/rules.d/40-basic-permissions.rules to say the following:

# USB devices (usbfs replacement)
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0664", GROUP="vboxusers"
SUBSYSTEM=="usb_device", MODE="0664", GROUP="vboxusers"Then, restart the udev service:

sudo /etc/init.d/udev restartNow, if you haven't done it already, make sure your user is part of the group vboxusers using the following command:

sudo usermod -G vboxusers -a `whoami`http://www.virtualbox.org/ticket/747

logged-off, logged on - no difference

powered off vm, exited virtualbox

started virtualbox. In console, turned off the USB 2 controller and created a device specific filter for the flash drive.

vboxmanage showed device busy

start Ubuntu VM and logged in

vboxmanage showed device as captured

no usb devices listed in lsusb

hovering over the USB icon on lower status bar shows no devices attached.

right-click on USB icon and selected the device - got the busy box again.

The rest of the info I have seen regarding Ubuntu deals with Ubuntu being the HOST OS.

I'm out of things to try from everything I've read.

I still think this is a problem with virtualbox and Windows XP Pro SP3 as the host and Linux (Ubuntu) as the guest.

Dave

EDIT-EDIT-EDIT:

Found this in a thread about wine and using it to kick off a vb process:

TerryE



Joined: 28 May 2008
Posts: 1884

Posted: Wed Jul 30, 2008 12:36 am Post subject:

--------------------------------------------------------------------------------

dangling participle wrote:
winehq db says it has problems with psexec
anyone with XPhome will have problems with PSexec. It assumes that you are running the full NT security and authentication model as implemented by NT4, W2K, XPpro. The MS boys gutted this for XPhome.
_________________

While I know wine has nothing to do with my problem, especially since I'm running a Windows host, but was curious if the things mentioning full NT security in XP Pro has anything to do with my problem. Perhaps I need to set something in the Windows host to give access to Linux guest for the USB devices?

[anewguy]

I've been trying tons of stuff, and got to thinking there may be a complication for my case:

I have libusb and GTK installed in Windows as well for cross-platform development with Linux. I'm starting to suspect MAYBE the libusb stuff installed in Windows may be affecting this. I may try uninstalling libusb from Windows host and see what happens.

dave

Okay - this got further. I removed libusb from Windows, then deleted all the filters from the VM. Closed VB, restarted VB, added an empty USB filter, started the VM. The device didn't show in the guest (Linux), however it now just says busy instead of captured with vboxmanage list usbhost. So, I right-clicked on the USB icon on the lower task bar and clicked on the device - it didn't give me a busy error box this time. But, it also still does not show in the guest (Ubuntu Linux) OS. I checked vboxmanage again and it showed the device as captured. So, it apparently is getting somewhere - I just can't see it yet in Ubuntu guest.

EDIT - forgot to mention - as soon as I deleted libusb from Windows host OS and plugged in the flash drive, I got a new hardware found for a vitrualbox usb device and it installed a driver - I never had that before either, so it must be getting further.

[anewguy]

Great news for me!! libusb in Windows host OS was the problem. I can see my USB devices in my guest Ubuntu OS now!!

Thanks everyone for your help!! i'll open a separate thread for the Windows host libusb and Ubuntu guest not working together.

[rich2600]

What worked for me, was watching the device manager, plugged in maxtor usb mass storage... loaded driver for it, loaded virtual box.. vbdriver took it over, but since the vbdriver is unsigned, didn't carry over the drive.

Check to make sure windows asks you to load unsigned drivers, win2003R2 doesn't allow it by default. So just reinstall the driver...



newbish mistake on my part....

[boneyard]

an old thread i know, but i found it when looking for a solution to my problem so perhaps others will also and find my solution helpful.

i had a similar issues (the message usb busy with previous request) with the latest virtualbox version 3.0.10. running vista home premium as host and running xp sp3 pro as guest.

after lots of trying and different attempts to connect / disconnect and so on i gave up and turned to vmware workstation which eventually pointed me to the issue.

it was an issue with the the usb driver (seehcri.sys) which Sony Ericsson installed with their phone software suite. once i rolled back all the USB Root Hubs to the intel version on the host system and not the Sony Eriscsson I got it working in vmware workstation and now also in virtualbox.