Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 325873 - app-emulation/virtualbox-bin-3.2.4: can't start virtual box with kernel 2.6.34
Summary: app-emulation/virtualbox-bin-3.2.4: can't start virtual box with kernel 2.6.34
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Patrick Lauer
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-27 19:56 UTC by David Relson
Modified: 2010-06-29 11:35 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
output of /etc/init.d/vboxdrv setup (vbox-install.log,2.16 KB, text/plain)
2010-06-27 19:57 UTC, David Relson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Relson 2010-06-27 19:56:27 UTC
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
Comment 1 David Relson 2010-06-27 19:57:48 UTC
Created attachment 236743 [details]
output of /etc/init.d/vboxdrv setup
Comment 2 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2010-06-27 20:08:25 UTC
Does this also happen with virtualbox-{bin,modules}-3.2.6?
Comment 3 David Relson 2010-06-28 04:03:35 UTC
Yes.  The problem is still present with 3.2.6
Comment 4 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2010-06-28 08:20:38 UTC
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
Comment 5 David Relson 2010-06-28 11:22:26 UTC
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!
Comment 6 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2010-06-29 11:35:18 UTC
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.