> Se estiver usando o fedora rs > > instale o kernel-headers veja se bate com o kernel q esta usando uname -a > > e o dkms > > depois roda de novo o /etc/init.d/vboxdrv setup > > > > No meu:
root@shibboleet:~# /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules * done. * Uninstalling old VirtualBox DKMS kernel modules Error! There are no instances of module: vboxhost 4.0.0 located in the DKMS tree. * done. * Trying to register the VirtualBox kernel modules using DKMS Error! Bad return status for module build on kernel: 2.6.38.4-1-helio (i686) Consult the make.log in the build directory /var/lib/dkms/vboxhost/4.0.0/build/ for more information. * Failed, trying without DKMS * Recompiling VirtualBox kernel modules * Look at /var/log/vbox-install.log to find out what went wrong Olhando nesse log (no final): make -f scripts/Makefile.build obj=/home/tmp/vbox.0 gcc -Wp,-MD,/home/tmp/vbox.0/linux/.SUPDrv-linux.o.d -nostdinc -isystem /usr/lib/ gcc/i686-linux-gnu/4.4.5/include -I/usr/src/linux-2.6.38.4/arch/x86/include -Iinclud e -include include/generated/autoconf.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototy pes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declar ation -Wno-format-security -fno-delete-null-pointer-checks -O2 -m32 -msoft-float -mr egparm=3 -freg-struct-return -mpreferred-stack-boundary=2 -march=i686 -mtune=generic -Wa,-mtune=generic32 -ffreestanding -fstack-protector -DCONFIG_AS_CFI=1 -DCONFIG_AS _CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -pipe -Wno-sign-compare -fno-asynchro nous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -Wframe-larger-than=1024 - fno-omit-frame-pointer -fno-optimize-sibling-calls -Wdeclaration-after-statement -Wn o-pointer-sign -fno-strict-overflow -fconserve-stack -I/lib/modules/2.6.38.4-1-helio /build/include -I/home/tmp/vbox.0/ -I/home/tmp/vbox.0/include -I/home/tmp/vbox.0/r0d rv/linux -I/home/tmp/vbox.0/vboxdrv/ -I/home/tmp/vbox.0/vboxdrv/include -I/home/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 -D RT_ARCH_X86 -DVBOX_WITH_64_BITS_GUESTS -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BAS ENAME=KBUILD_STR(SUPDrv_linux)" -D"KBUILD_MODNAME=KBUILD_STR(vboxdrv)" -c -o /home/ tmp/vbox.0/linux/.tmp_SUPDrv-linux.o /home/tmp/vbox.0/linux/SUPDrv-linux.c In file included from /home/tmp/vbox.0/include/VBox/types.h:30, from /home/tmp/vbox.0/linux/../SUPDrvInternal.h:35, from /home/tmp/vbox.0/linux/SUPDrv-linux.c:31: /home/tmp/vbox.0/include/iprt/types.h:97: fatal error: linux/autoconf.h: No such fil e or directory compilation terminated. make[2]: *** [/home/tmp/vbox.0/linux/SUPDrv-linux.o] Error 1 make[1]: *** [_module_/home/tmp/vbox.0] Error 2 make: *** [vboxdrv] Error 2 Uma vez que eu compilei meu próprio kernel usando make-kpkg, foi só arrumar o link: root@shibboleet:vboxdrv# cd /usr/src/linux/include/linux/ root@shibboleet:linux# ln -s ../generated/autoconf.h . Finalmente: root@shibboleet:linux# /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules * done. * Uninstalling old VirtualBox DKMS kernel modules * done. * Trying to register the VirtualBox kernel modules using DKMS * done. * Starting VirtualBox kernel modules * done. []´s Helio Loureiro http://helio.loureiro.eng.br http://hloureiro.multiply.com http://twitter.com/helioloureiro