installed: app-emulation/virtualbox-bin-3.2.4-r1 app-emulation/virtualbox-modules-3.2.4 An attempt to start virtualbox tells me to run /etc/init.d/vboxdrv setup. Running /etc/init.d/vboxdrv setup fails. Log file /var/log/vbox-install.log says include/generated/autoconf.h doesn't exist. /usr/src/linux is a symlink to /usr/src/linux-2.6.34-gentoo-r1 /usr/src/linux-2.6.34-gentoo-r1/include/generated/autoconf.h _does_ exist (and is timestamped today, approx 15 minutes ago) Reproducible: Always Steps to Reproduce: 1./etc/init.d/vboxdrv setup 2. 3. Actual Results: root@osage linux # /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel module ... [ ok ] * Removing old VirtualBox netadp kernel module ... [ ok ] * Removing old VirtualBox netflt kernel module ... [ ok ] * Removing old VirtualBox kernel module ... [ ok ] * Recompiling VirtualBox kernel module ... * Look at /var/log/vbox-install.log to find out what went wrong
Created attachment 236743 [details] output of /etc/init.d/vboxdrv setup
Does this also happen with virtualbox-{bin,modules}-3.2.6?
Yes. The problem is still present with 3.2.6
By looking more closely to your bug description it seems like you were installing virtualbox-bin by hand and not via portage (we do not provide /etc/init.d/vboxdrv in our packages). Please uninstall your manual installation and then install the package we provide via emerge -v virtualbox-bin
I _had_ used emerge to update virtualbox-bin and virtualbox-modules. Emerge created the vbox modules in /lib/modules/.../misc. When I started VirtualBox using Gnome's start menu, I got a popup window telling me to run "/etc/init.d/vboxdrv setup". Running the command gives the error I reported. After using emerge -C and emerge -v to remove/install virtual box, I used the command line to start VirtualBox. This produced the following warning: WARNING: The VirtualBox kernel modules are not loaded. Please load all the needed kernel modules by: for m in vbox{drv,netadp,netflt}; do modprobe $m; done You will not be able to start VMs until this problem is fixed. Manually loading the modules (as suggested), solved the problem and all is now good. Thank you for your time!
Sorry for the confusion from my side. I never started VirtualBox without its kernel modules being loaded so I never saw that message on my systems. I'm glad you figured out how to solve your problem and I wish you as much fun with VBox as I have :) Marking as INVALID as it's not a bug in our packages.