Page 1 of 2
modprobe vboxdrv failed
Posted: 6. Sep 2008, 16:15
by benke
Hi all.
Sorry for bothering you but I just downloaded VirtualBox-2.0.0-36011-Linux_x86.run but having problem with kernel module. When I issue
/etc/rc.d/rc.vboxdrv setup it says
Code: Select all
Stopping VirtualBox kernel module ...done.
Removing old VirtualBox kernel module ...done.
Recompiling VirtualBox kernel module ...done.
Starting VirtualBox kernel module ...failed!
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
The last line got with dmesg is
Code: Select all
vboxdrv: Unknown symbol register_cpu_notifier
If I try to start VirtualBox, I get this message:
Code: Select all
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (2.6.20.3) or it failed to
load. Please recompile the kernel module and install it by
sudo /etc/init.d/vboxdrv setup
You will not be able to start VMs until this problem is fixed.
I am using VectorLinux 5.8, kernel is 2.6.20.3. Thank you in advance.
Posted: 6. Sep 2008, 16:22
by Sasquatch
I assume you didn't have a previous version of VB running, else there might be some residual config that is causing this problem. Have you already tried a reboot? If you don't really need the added features of 2.0, use the maintenance release 1.6.6 instead.
Posted: 6. Sep 2008, 16:31
by benke
Thank you for fast reply.
No, I didn't had previous version running. I uninstalled 2.0.0 and now I am downloading 1.6.6...
Posted: 6. Sep 2008, 16:34
by stefan.becker
More Infos.
CPU?
Distribution 32 Bit or 64 Bit?
Kernel-source/Header installed in same version than kernel?
gcc installed?
And try this: "sudo /etc/init.d/vboxdrv setup"
If failing, post thge messages in the logfile (path and name in the message).
Posted: 6. Sep 2008, 17:04
by benke
CPU is Sempron 2500, VectorLinux 5.8 is 32 bit distribution, gcc is installed and kernel source version is same as kernel - 2.6.20.3. vboxdrv goes to /etc/rc.d (it's Slackware-like):
Code: Select all
/etc/rc.d/rc.vboxdrv setup
Stopping VirtualBox kernel module ...done.
Removing old VirtualBox kernel module ...done.
Recompiling VirtualBox kernel module ...done.
Starting VirtualBox kernel module ...failed!
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
tail -f /var/log/vbox-install.log
Building modules, stage 2.
make -f /usr/src/linux-2.6.20.3/scripts/Makefile.modpost
scripts/mod/modpost -i /usr/src/linux-2.6.20.3/Module.symvers -I /tmp/vbox.0/Module.symvers -o /tmp/vbox.0/Module.symvers -w /tmp/vbox.0/vboxdrv.o
WARNING: "register_cpu_notifier" [/tmp/vbox.0/vboxdrv.ko] undefined!
gcc -m32 -Wp,-MD,/tmp/vbox.0/.vboxdrv.mod.o.d -nostdinc -isystem /usr/lib/gcc/i486-slackware-linux/3.4.6/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O2 -pipe -msoft-float -mregparm=3 -mpreferred-stack-boundary=2 -fno-unit-at-a-time -march=i586 -ffreestanding -maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -Iinclude/asm-i386/mach-default -fomit-frame-pointer -Wdeclaration-after-statement -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(vboxdrv.mod)" -D"KBUILD_MODNAME=KBUILD_STR(vboxdrv)" -DMODULE -c -o /tmp/vbox.0/vboxdrv.mod.o /tmp/vbox.0/vboxdrv.mod.c
ld -m elf_i386 -m elf_i386 -r -o /tmp/vbox.0/vboxdrv.ko /tmp/vbox.0/vboxdrv.o /tmp/vbox.0/vboxdrv.mod.o
make[1]: Leaving directory `/usr/src/linux-2.6.20.3'
1.6.6 works, with lsmod I can see that module is loaded...
Posted: 6. Sep 2008, 17:20
by stefan.becker
Dont know Vector Linux. For Suse there is a package called "kernel-syms" needed.
Probably here failing something like that?
Posted: 6. Sep 2008, 17:21
by Sasquatch
1.6.6 works, with lsmod I can see that module is loaded...
So does it also work?
Posted: 6. Sep 2008, 17:29
by benke
Yes, 1.6.6 works just fine, just started Slax ISO under VectorLinux.
Posted: 6. Sep 2008, 18:46
by TerryE
register_cpu_notifier is part of the SMP support in the Linux kernel. I guess that this is missing from the VectorLinux 2.6.20 kernel. Well as long as 1.6.6 works.
Posted: 6. Sep 2008, 19:23
by benke
With make xconfig I can see that it have 'Y' under 'Symmetric multi-processing support (SMP)'...
Re: modprobe vboxdrv failed
Posted: 6. Jul 2009, 22:45
by benke
Code: Select all
vboxdrv: Unknown symbol register_cpu_notifier
appeared upon installation of VirtualBox 3.0.0 too
Re: modprobe vboxdrv failed
Posted: 7. Jul 2009, 17:06
by benke
VirtualBox 3.0.0 works under VectorLinux 6.0 which works under VirtualBox 1.6.6 under VectorLinux 5.8
Looks like it's time for OS upgrade...
Re: modprobe vboxdrv failed
Posted: 7. Jul 2009, 23:18
by Sasquatch
Benke, Starting VB is one thing, running a VM will really test the module and you can't do that inside a VM (nested won't work). Did you run the command the TS used?
Re: modprobe vboxdrv failed
Posted: 7. Jul 2009, 23:41
by TerryE
Gosh, I am not sure that I would get any work done with the distraction of that desktop
As S says, installing and running the VirtualBox GUI is one thing. Running a nested VM is entirely another. If that works I'd be surprised and interested to know.
Re: modprobe vboxdrv failed
Posted: 8. Jul 2009, 00:06
by benke
Okay, will try to run Slax, Puppy or something like this to be sure that it really works. Thanks for pointing me but kernel module is loaded...