Comments on VirtualBox 2: How To Pass Through USB Devices To Guests On An Ubuntu 8.10 Host

Actually, if all you need is access to a usb mass storage device ( sorry no usb webcam ) you can easily do that with the OSE version. If linux is the host simply add another shared folder to the host's /media directory. When you insert a usb device it is automatically  mounted to  /media on the host and visible  to the guest through the shared folder.

The advantage is that the host is always in control of the device and the system and the user never gets confused over when or if and by whom the device was unmounted. I haven't figured out yet how to do that on a Windows host.

This I've known with the latest version of VB.  I also found great success of adding a line in fstab for VB:

none /proc/bus/usb usbfs devgid=500,devmode=664 0 0

You might be asking why I had great success by adding that line, well I bought my parent TomTom 130 for a present and they are running Hardy (at that time), and when I updated the device I was using Ubuntu 8.10 and Windows XP was able to see the GPS. So when I gave them their present, their VB Windows XP did not see their GPS, so I did a fresh install of Ubuntu 8.10 and when I attached their GPS to VB Windows XP, XP did not see the device. So I remembered what I added that entry into fstab, so I ssh into my machine and copied that line to my parent machine and their VB saw their GPS device.

Hope this helps people.

The key to this issue, not just for webcam but other devices too, is this line in your /etc/fstab:

none /proc/bus/usb usbfs devgid=500,devmode=664 0 0 

The devgid has to match your gid of your vboxusers group. For some reason the gid changed on my system, I don't know how or why but I suspect it was part of the numerous updates that vbox urges you to do. If you need to change this value a reboot of your host will likely be required due to proc/bus/usb being busy.

BTW, the fstab entry was done by the installation script so there is no longer a need to insert it manually.

Nice howto, thanks.

But, it is still not possible to use the webcam, is there a method to slove that problem?

Greetz,
Kris

I am running a Windows XP virtual machine on a Ubuntu Karmic host.  Your solution does not work.  You say, "After the guest has started, right-click on the USB icon in the VirtualBox "task bar" and select the USB device that you want to use in the guest," but the mass storage USB device is grayed out (its listed, but grayed out), and cannot be selected.  And, yes, I am part of the vboxusers group.

If the devices are greyed out, be sure to add your user in the group vboxuser.  After your next logon everything will be working.

I'm having a problem accessing a usb stick in Windows 10 using VB  with Linux.  I have noted my hardware and software below and a description of the problem.Acer E1-572-6829 laptop i5 processor, 1.6gHz processor, 6GB ram, 1TB SS HD. Running Linux Mint Tessa 19.1 with all updates, VB 6.0.6, with Guest additions and Extension pack of the same version with Windows 10 professional. As distros for VB have been noted as not supporting usb, I downloaded the above VB, Guest additions and the Extension pack for the VB website.I have clicked added myself in Users and Groups>VBoxusersI can register the usb stick, I can see it in the Guest OS and select it on the devices>usb.  When I select it caja (linux filemanager) stops displaying it as available and I hear a tone that the management of the stick has changed to VB.  However I can not see it in Windows file manager. The reverse is also true, I can de-select it and caja will display the stick, which I can access.In the past (earlier version of VB and windows - not sure of either or if they were even on this laptop) when I clicked on the usb stick I would hear the tone, linux file manager would give up control and I would see the stick in windows filemanager.Any help would be appreciated.Thanks,Lou

Update to usb issue I wrote about earlier today.

I changed from usb 1 to usb 2 and it is working like I would have expected. Note: this has to occur prior to executing VB guest system.

So the issue is resolved, hopefully this resolution may help some others.

Thanks for having a site to help out and the abiltiy to comment.

Best,

Lou