In VirtualBox with virtualbox-modules-3.2.10.ebuild, USB Device are grayed out (unavailable) to guest. IMHO this is because the permission mode in udev rule in virtualbox-modules-3.2.10 src_install should read 0664. Besides this, /proc/bus/usb is already mounted by localmount init script with mode=0664 and devgid=85 (usb). Thus, I think also pointing the user to add his account to group usb is an appropriate solution, because uncommenting the udev rules in 10-virtualbox.rules is effect-less in this case. Feedback appreciated. Reproducible: Always Steps to Reproduce: 1. start guest, try to add usb device 2. device is unavailable, even with udev rules commented out 3. adding user to group usb solves this Problem Actual Results: Can't connect usb devices to host. Expected Results: Pass through device to guest. app-emulation/virtualbox-bin-3.2.10 app-emulation/virtualbox-modules-3.2.10 ================================================================= System uname: Linux-2.6.34-gentoo-r6-i686-Intel-R-_Core-TM-2_Duo_CPU_E6750_@_2.66GHz-with-gentoo-1.12.13 Timestamp of tree: Wed, 20 Oct 2010 07:15:01 +0000 distcc 3.1 i686-pc-linux-gnu [disabled] ccache version 2.4 [enabled] app-shells/bash: 4.0_p37 dev-java/java-config: 1.3.7, 2.1.11 dev-lang/python: 2.4.6, 2.5.4-r3, 2.6.5-r2, 3.1.2-r3 dev-util/ccache: 2.4-r7 dev-util/cmake: 2.6.4-r3 sys-apps/baselayout: 1.12.13 sys-apps/sandbox: 1.6-r2 sys-devel/autoconf: 2.13, 2.65 sys-devel/automake: 1.4_p6-r1, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r4, 1.9.6-r3, 1.10.3, 1.11.1 sys-devel/binutils: 2.20.1-r1 sys-devel/gcc: 4.1.2, 4.3.4, 4.4.3-r2 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.2.6b sys-devel/make: 3.81 virtual/os-headers: 2.6.30-r1 ACCEPT_KEYWORDS="x86" ACCEPT_LICENSE="*" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -m32 -march=core2 -mtune=core2 -pipe -fomit-frame-pointer -mmmx -msse -msse2 -msse3 -mssse3 -mfpmath=sse" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config /var/lib/hsqldb" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/sandbox.d /etc/splash /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c" CXXFLAGS="-O2 -m32 -march=core2 -mtune=core2 -pipe -fomit-frame-pointer -mmmx -msse -msse2 -msse3 -mssse3 -mfpmath=sse" DISTDIR="/usr/portage/distfiles" FEATURES="assume-digests ccache distlocks fixpackages news parallel-fetch protect-owned sandbox sfperms strict unmerge-logs unmerge-orphans userfetch userpriv usersandbox" GENTOO_MIRRORS="ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo ftp://mirror.muntinternet.net/pub/gentoo/ ftp://mirror.switch.ch/mirror/gentoo/" LANG="en_US.UTF-8" LC_ALL="en_US.UTF-8" LDFLAGS="-Wl,-O1 -Wl,--as-needed" LINGUAS="de en" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage/layman/sunrise /usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
This issue has been addressed upstream. Although you might be able to solve your problem temporarly by renaming the /etc/udev/rules.d/10-virtualbox.rules to /etc/udev/rules.d/80-virtualbox.rules (depending on your setup), the upstream solution uses an individually created device tree. For the upstream discussion see http://www.virtualbox.org/ticket/5345. If you upgrade to virtualbox-4.x be sure to take a look at http://bugs.gentoo.org/show_bug.cgi?id=356215. The ebuild in the tree might lead to similar problems due to wrong udev rules.
There is a solution for this problem as well as rewritten, tested and working ebuilds for newer versions of virtualbox - what keeps this bug from being closed?
virtualbox-3 is no longer in the tree. Closing as obsolete.
