VIrtualBox (vboxdrv) is either not loaded

[pedenski]

Im getting this error in virtualbox

Kernel driver not installed (rc=-1908)

The virtualbox linux kernel driver (vboxdrv) is either not laoded or there is a permission problem with /dev/vboxdrv. please reinstall the kernel module by executing

/etc/init.d/vboxdrv setup

-----------------

[root@zym zild]# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Trying to register the VirtualBox kernel modules using DKMSError! echo
Your kernel headers for kernel 3.3.4-3.fc16.i686 cannot be found at
/lib/modules/3.3.4-3.fc16.i686/build or /lib/modules/3.3.4-3.fc16.i686/source.
[FAILED]
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [FAILED]
(Look at /var/log/vbox-install.log to find out what went wrong)
[root@zym zild]#

can someone help me resolve this?

[glennzo]

If you've just installed VirtualBox you will need to install kernel headers and gcc at the very least.

PHP Code:

su
<password>
yum install kernel-headers gcc
/etc/init.d/vboxdrv setup 


That should get VirtualBox working. If not, intstall kernel-devel and try again.

Oh, what did the log tell you?

[pedenski]

Hi sir, this is not a fresh install, VBOX was working fine since yesterday. im not sure if my recent upgrade of fedora caused VBOX not to work.

I have to install kernel-devel too
and run
/etc/init.d/vboxdrv setup

thanks for your help, its now working.

i looked over into the /var/log/ there were no vbox-install.log; how strange, really.

also may i just ask, since im new to linux; what do you think caused it not to work. looking at the errors it tells
Your kernel headers for kernel 3.3.4-3.fc16.i686, why suddenly my kernel headers disappeared?

[glennzo]

Was there a kernel update? If so, that is the cause of the issue and VirtualBox will need to be rebuilt as stated above. If you install DKMS then theoretically the rebuilding will take place automatically when the system boots into the new kernel and you will need to do nothing.

[pedenski]

lazy as this sound, but i never paid attention on the release notes of the recent kernel patch, heck didnt even know there's such thing. I installed my VBOX using yum and thought every module/plugin or whatever is already included on the package. I had no idea that DKMS is needed.

grazias sir.

[glennzo]

DKMS is needed only if you want the modules automatically rebuilt. You can always manually rebuild after a kernel update.

[sea]

Uhm let me jump in for a single question..
So i can remove dkms, if i rebuilt the kernel modules with /etc/initd/vboxdrv setup manualy after a kernel update?

[glennzo]

Originally Posted by sea

Uhm let me jump in for a single question..
So i can remove dkms, if i rebuilt the kernel modules with /etc/initd/vboxdrv setup manualy after a kernel update?

As long as nothing else depends on it. I, for whatever reason, don't install DKMS when I install VirtualBox. I guess I prefer the pain and suffering when I run VirtualBox for the first time after a kernel update and it tells me that there are errors with modules. Then I close VirtualBox, open a terminal and run /etc/init.d/vboxdrv setup, allow it to complete and run VirtualBox again.

If DKMS rebuilds the modules upon reboot it slows the overall boot time. Maybe that's why I don't bother with it.

[Adunaic]

I am having teh same problem. Virtual Box was fine and has now stopped working.

I have ran the command VBox suggested and made sure headers etc. are installed.

[root@localhost user]# yum list kernel*
Installed Packages
kernel.i686                          3.3.0-4.fc16           @updates/$releasever
kernel.i686                          3.3.4-1.fc16           @updates            
kernel.i686                          3.3.4-3.fc16           @updates            
kernel-PAE.i686                      3.3.4-3.fc16           @updates            
kernel-PAE-devel.i686                3.3.4-3.fc16           @updates            
kernel-devel.i686                    3.3.4-1.fc16           @updates            
kernel-devel.i686                    3.3.4-3.fc16           @updates            
kernel-headers.i686                  3.3.4-3.fc16           @updates            
Available Packages
kernel-PAEdebug.i686                 3.3.4-3.fc16           updates             
kernel-PAEdebug-devel.i686           3.3.4-3.fc16           updates             
kernel-debug.i686                    3.3.4-3.fc16           updates             
kernel-debug-devel.i686              3.3.4-3.fc16           updates             
kernel-doc.noarch                    3.3.4-3.fc16           updates             
kernel-tools.i686                    3.3.4-3.fc16           updates             
kernel-tools-devel.i686              3.3.4-3.fc16           updates             
[root@localhost user]# uname -r
3.3.4-3.fc16.i686.PAE

I installed Virtual Box using Autoplus. Any suggestions?

[glennzo]

Originally Posted by Adunaic

I am having teh same problem. Virtual Box was fine and has now stopped working.

I have ran the command VBox suggested and made sure headers etc. are installed.

[root@localhost user]# yum list kernel*
Installed Packages
kernel.i686                          3.3.0-4.fc16           @updates/$releasever
kernel.i686                          3.3.4-1.fc16           @updates            
kernel.i686                          3.3.4-3.fc16           @updates            
kernel-PAE.i686                      3.3.4-3.fc16           @updates            
kernel-PAE-devel.i686                3.3.4-3.fc16           @updates            
kernel-devel.i686                    3.3.4-1.fc16           @updates            
kernel-devel.i686                    3.3.4-3.fc16           @updates            
kernel-headers.i686                  3.3.4-3.fc16           @updates            
Available Packages
kernel-PAEdebug.i686                 3.3.4-3.fc16           updates             
kernel-PAEdebug-devel.i686           3.3.4-3.fc16           updates             
kernel-debug.i686                    3.3.4-3.fc16           updates             
kernel-debug-devel.i686              3.3.4-3.fc16           updates             
kernel-doc.noarch                    3.3.4-3.fc16           updates             
kernel-tools.i686                    3.3.4-3.fc16           updates             
kernel-tools-devel.i686              3.3.4-3.fc16           updates             
[root@localhost user]# uname -r
3.3.4-3.fc16.i686.PAE

I installed Virtual Box using Autoplus. Any suggestions?

What are the errors you see when running /etc/init.d/vboxdrv setup?

[Adunaic]

I will put this error down to jet lag.

I finally found the log file (which I had just not seen before) and it turned out that I needed to install "make".

Thanks for the quick reply though.

[glennzo]

No problem. I just tried to run VirtualBox on my Fedora 17 install and it failed in the same manner that it did for everyone in this thread. Running vnoxdrv setup fixed it.

[lagcMoro]

hello

this is my first participation

i had the same problem, that I have now solved:

in 32 bit:

tape this command in terminal:

yum install dkms binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-pae-devel


and:

/etc/init.d/vboxdrv setup

in 64 bit:

yum install dkms binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel

/etc/init.d/vboxdrv setup

restart the system and it works!

[earlati]

Hello everyone
I also have the same problem.
After the last upgrage of kernel I can't no more compile the VisrtualBox module, as show below.
I check the log files but I didn't understand what can I do to solve the problem.
Any suggestions ?

Regards, Enzo

[root@enzo7 ~]# /etc/rc.d/init.d/vboxdrv setup
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Trying to register the VirtualBox kernel modules using DKMSError! Bad return status for module build on kernel: 3.5.1-1.fc17.i686.PAE (i686)
Consult /var/lib/dkms/vboxhost/4.1.16/build/make.log for more information.
[FAILED]
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [FAILED]
(Look at /var/log/vbox-install.log to find out what went wrong)

[root@enzo7 ~]# tail -22 /var/lib/dkms/vboxhost/4.1.16/build/make.log
make: Entering directory `/usr/src/kernels/3.5.1-1.fc17.i686.PAE'
LD /var/lib/dkms/vboxhost/4.1.16/build/built-in.o
LD /var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/built-in.o
CC [M] /var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/linux/SUPDrv-linux.o
CC [M] /var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/SUPDrv.o
CC [M] /var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/SUPDrvSem.o
CC [M] /var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/r0drv/alloc-r0drv.o
CC [M] /var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/r0drv/initterm-r0drv.o
CC [M] /var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/r0drv/memobj-r0drv.o
CC [M] /var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/r0drv/mpnotification-r0drv.o
CC [M] /var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/r0drv/powernotification-r0drv.o
CC [M] /var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
CC [M] /var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o
CC [M] /var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/r0drv/linux/initterm-r0drv-linux.o
CC [M] /var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o
/var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjLinuxDoMmap’:
/var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1150:9: error: implicit declaration of function ‘do_mmap’ [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[2]: *** [/var/lib/dkms/vboxhost/4.1.16/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o] Error 1
make[1]: *** [/var/lib/dkms/vboxhost/4.1.16/build/vboxdrv] Error 2
make: *** [_module_/var/lib/dkms/vboxhost/4.1.16/build] Error 2
make: Leaving directory `/usr/src/kernels/3.5.1-1.fc17.i686.PAE'

[root@enzo7 ~]# tail -8 /var/log/vbox-install.log
if [ "-pg" = "-pg" ]; then if [ /tmp/vbox.0/r0drv/linux/initterm-r0drv-linux.o != "scripts/mod/empty.o" ]; then /usr/src/kernels/3.5.1-1.fc17.i686.PAE/scripts/recordmcount "/tmp/vbox.0/r0drv/linux/initterm-r0drv-linux.o"; fi; fi;
gcc -Wp,-MD,/tmp/vbox.0/r0drv/linux/.memobj-r0drv-linux.o.d -nostdinc -isystem /usr/lib/gcc/i686-redhat-linux/4.7.0/include -I/usr/src/kernels/3.5.1-1.fc17.i686.PAE/arch/x86/include -Iarch/x86/include/generated -Iinclude -include /usr/src/kernels/3.5.1-1.fc17.i686.PAE/include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m32 -msoft-float -mregparm=3 -freg-struct-return -mpreferred-stack-boundary=2 -march=i686 -mtune=generic -maccumulate-outgoing-args -Wa,-mtune=generic32 -ffreestanding -fstack-protector -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_AVX=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -Wframe-larger-than=1024 -Wno-unused-but-set-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls -g -pg -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -DCC_HAVE_ASM_GOTO -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -I/lib/modules/3.5.1-1.fc17.i686.PAE/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -I/tmp/vbox.0/vboxdrv/ -I/tmp/vbox.0/vboxdrv/include -I/tmp/vbox.0/vboxdrv/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DCONFIG_VBOXDRV_AS_MISC -DRT_ARCH_X86 -DVBOX_WITH_64_BITS_GUESTS -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(memobj_r0drv_linux )" -D"KBUILD_MODNAME=KBUILD_STR(vboxdrv)" -c -o /tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.o /tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c
/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjLinuxDoMmap’:
/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:1150:9: error: implicit declaration of function ‘do_mmap’ [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[2]: *** [/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.o] Error 1
make[1]: *** [_module_/tmp/vbox.0] Error 2
make: *** [vboxdrv] Error 2