Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 14.1, 14.2
After some looking around my system, I added my regular usid to the vboxusers group. Not sure if this will help or not, it shouldn't hurt anything. I also have regular users added to the USB group. That shouldn't hurt either.
You know your usb devices show up under /proc/bus/usb and then under the sub-dirs /001 /002 etc depending on sockets etc. The devices you have plugged in will show up as a file under each of those and this filename will be probably 002, 003 etc - the file showing 001 will be the actual socket.
Set the permissions of the _device_ file to be 'rwx' for group 'vboxusers' and/or 'others'.
I'm happy doing many things at the CLI but the chmod/chown permissions is not one of these so I use that great terminal prog Midnight Commander which has carried on working in its own way without all the hassle that has appeared in recent Linux times like KDE4 and hal/udev or kernel stuff giving us problems like yours and mine (other thread).
M.C. has its own drop-down menu to do all manner of things to files/directories and the chown/chmod bits give a nice visual feedback of the octal - 664/775 - type so you can see what applying 'rwx' for each set will do number-wise.
I said above to change the permissions for the 2 groups beside 'owner' as "and/or" meaning that for my own bizarre experience I found that one distro would need both done whereas another needed the 'others' only.
And that was despite the 'owner' being set as me or the actual login user.
Even having fstab entries to get the /proc/bus/usb coming up _and_ giving it and an entry for usbfs device node permissions, all my usb devices could be used but not in VBox with recent kernels. When I did the permissions change manually on the device entries as above - eureka!!!
Christ knows what actual code that's running in those newer kernels and/or newer hal/udev causing this grief.
Glenn, no, I said the /proc/bus/usb directories. And then you drill down to the seperate /001 /002 ... dirs where each of those will have a file entry for the device plugged in. It's the file entry for the device you need to chown.
The file 'devices' that's in /proc/bus/usb will list all the usb stuff plugged in and should show which bus entry it's in. For your problem device, look for its name in that file and then see which actual bus it's plugged into - /001 or /002 etc - then go to /001 and there another file named 002 (because the socket for that bus will be 001) will relate to your actual usb device.
Double check that by unplugging all stuff and see that there are only the 001 files in those sub-dirs., Wait and then plug 1 device back into a usb socket. The time stamp of the file that appears will be obviously different from the "socket 001" file.
i went back and looked... i guess the PUEL version is supposed to have usb support, the OSE version does not. if you get it figured out, i'm still subscribed to this thread. in the meantime, i'm using VMware. i needed to talk to a TI evaluation module for a project, and couldn't wait around for an answer on VBox... if you get it figured out, great, i think VBox runs faster and smoother than VMware.... but in the meantime, VMware is working for what i need it for.
Installed no problems, so I know the sources are installed correctly(?)
find and remove all except the virtual-machines and HardDisks. (winxpsp2 in this case)
After that I rebooted, then updatedb, and searched again.
I found some stale links to vbox programs in /usr/bin, sudo rm -rf
Once satisfied I had removed all instances of vbox,
I then reinstalled ver (VirtualBox-3.2.6-63112-Linux_amd64.run)
Once again before starting the virtual machine I was able to select which usb devices I wanted access to,
Namely the Joystick. Logitech, Extreme 3D. Even now, the winxp VM is running, in the Oracle VM window it shows one usb device active, but from the winxp VM they are all greyed out and when moused-over, the message is
Indicates the activity of the attached usb devices: No usb devices attached
The US banned this game after 9/11 because of the realism of tech involved for radar, communications, tactics and weapons systems.
They managed to cripple the game with the agp-2.0 code 8 or 9 odd years ago (win2k).
So, I'm sus, but I don't believe it.
changed primary user of vboxusers (user) to vboxusers, and made glenn a member of the vboxusers.
vboxusers has vboxusers, glenn, root, usb and games as members of the group.
(I had glenn as the primary user of vboxusers (user)) reboot!