include/linux/compiler-version.h -include. Gcc -Wp,-MMD,/tmp/vbox.0/linux/.SUPDrv-linux.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/7/include -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include. scripts/Makefile.build obj=/tmp/vbox.0 \ The kernel was built by: gcc (Ubuntu 11.2.0-7ubuntu2) 11.2.0 Warning: the compiler differs from the one used to build the kernel Make: warning: -jN forced in submake: disabling jobserver mode. Modprobe only seems to like already-installed modules, but insmod seems happy to inset the sudo insmod sudo /etc/init.d/vboxdrv startĪfter this, virtualbox seemed to run ok again! I would imagine that you can just copy the module to the correct place so that modprobe finds it upon bootup.Make V=1 CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /lib/modules/5.15.0-051500-generic/build M=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j8 modules I wasn't sure if the old existing module would still be compatible with my new kernel. So I tried to find the module, wondering where it had find / -mount -iname vboxdrv.ko 2>/dev/null /lib/modules/2.6.22-14-generic/misc/vboxdrv.koįound it, but it's not installed in the correct place due to a kernel uname -r * Starting VirtualBox kernel module vboxdrv
#VIRTUALBOX KERNEL DRIVER NOT INSTALLED UPGRADE#
I fixed it after suspecting that my Gutsy kernel upgrade was interfering with the kernel sudo /etc/init.d/vboxdrv start Other than these two things, I'm out of ideas. The reinstall SHOULD go smoothly, including building the kernel module. Now you can reinstall virtualbox by simply double-clicking on the file. If that is not the problem, then open a terminal and completely remove virtualbox - "sudo apt-get autoremove virtualbox -purge" If so, remove everything EXCEPT virtualbox 1.6.2 (and make sure it is the version for Hardy!) and then run "sudo /etc/init.d/vboxdrv setup" Check to see if there are still some modules from the OSE version installed. First of all, I'd like you to go to System -> Administration -> Synaptic Package Manager and then search for virtualbox.
#VIRTUALBOX KERNEL DRIVER NOT INSTALLED WINDOWS#
and I'm having no trouble running Windows 2000 and Vista Home Premium. I've got Virtualbox 1.6.2 installed on two machines. Yes I have rebooted (this computer gets shut off every night).Īnd no, KERN_DIR=/usr/src/linux did not work.I'm honestly stumped. To the first question: yes, tried it both ways
I am on Ubuntu 8.04 and have not changed the kernel (e.g. So I basically just need to know where the KERN_INCL dir should be. Makefile:154: *** Error: unable to find the include directory for your current Linux kernel. So I do sudo KERN_DIR=/boot/ /etc/init.d/vboxdrv setup
Makefile:127: *** Error: unable to find the sources of your current Linux kernel. * Look at /var/log/vbox-install.log to find out what went wrong * Stopping VirtualBox kernel module * done. So I run it and get sudo /etc/init.d/vboxdrv setup I can not start a vm on virtualbox I get the this error
0 kommentar(er)
