Mark Knecht wrote:
On Sun, Jul 24, 2011 at 5:16 PM, Daniel Wagener<st...@gmx.net> wrote:
On Sun, 24 Jul 2011 17:09:13 -0700
Mark Knecht<markkne...@gmail.com> wrote:
Hi,
I just got around to trying my Virtualbox VMs under the new 3.0.0
kernel and they aren't working. It says vboxdrv is not set up. I drop
back to 2.6.39 and they run fine. Please note I really mean only the
VMs won't start. The Vbox GUI runs fine but then cannot start the VMs.
I used make oldconfig to get 3.0.0 working so maybe that caused the
problem but I don't yet see what's wrong looking at the config files.
Most likely this is some problem caused by the new numbering but I
Googled around looking for a solution and didn't find one. Has anyone
else here checked Virtualbox under the new kernel?
Note that VMWare seems to be running fine under 3.0.0, only
Virtualbox is failing.
Thanks,
Mark
You know that these Modules have to be compiled against the running
kernel? A re-emerge should do:
emerge -1av virtualbox-modules
Almost forgot: youd also have to reload these modules via modprobe (or
rebooting *hides*)
I'm about 500% I did all that but I'll do it again just to be sure.
I use modules-rebuild -X rebuild to catch all the modules I need to
rebuild as well as a few applications that over the years had problems
with kernel or xorg-server changes. My list of modules& apps now
numbers about 8 and I know virtualbox-modules is part of that list.
None the less when I get back to that machine I'll do it again.
Thanks,
MArk
Just to mention something stupid that I would do, and have done, don't
forget to make sure the symlink is pointing to the new kernel. I did
that the other day with the nvidia drivers. I scratched my head for
minute because I did for once remember to rebuild the drivers before I
rebooted. Sort of funny in a way. lol It's usually the other way
around. One step forward, one step back.
Dale
:-) :-)
