virtualbox.org End user forums for VirtualBox Advanced search Board index Change font size FAQ Login Information The requested topic does not exist. But anyway, it is very easy to fix the issue. Leave a comment to let us know how we could improve. Specify KERN_DIR=
Postby pschaff » 2012/05/18 18:15:54 maui_muc wrote:I did a yum update and it installed a couple of new packages. Where does it has to point at?That should not be necessary. Specify KERN_DIR=
What I would suggest is to: Take a snapshot of your current VM Update kernel, kernel-devel, boot into the new kernel Clean up the VirtualBox installation, incl. So if this command fails: make -C /usr/src/kernels/$(uname -r)/build kernelrelease you should install the Linux headers by: sudo apt-get install linux-headers-$(uname -r) For further details, please check this post. Please reinstall the kernel module by executing '/sbin/rcvboxdrv setup' Solution : Reinstall the kernel module As I mentioned before problem happens if you did not installed kernel-headers before install VirtualBox. We Acted.
I wanted to install the VB Guest Additions as described in the Wiki, http://wiki.centos.org/HowTos/Virtualiz ... Top maui_muc Posts: 3 Joined: 2012/05/18 10:37:04 Re: CentOS 6.2: VirtualBox Guest Additions -> Error: unable to find the sources ... Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Contact Preferences User Management Account Maintenance My Profile Notifications Help Log Unable To Find The Sources Of Your Current Linux Kernel Ubuntu Yes No We appreciate your feedback.
The installation process fails and the log files are saying: Code: Select alltmp/vbox.0/Makefile.include.header:94: *** Error: unable to find the
sources of your current Linux kernel. Unable To Find The Sources Of Your Current Linux Kernel Debian A surprising conjecture about twin primes What is the intuition behind the formula for the average? Any suggestions what I did wrong? Let's speed that file sentence searching program Second law of thermodynamics doubt Can Mirror Image still work while being grappled?
Down-voting might cost you karma, but you should consider doing so for incorrect or clearly detrimental questions and answers. Unable To Find The Sources Of Your Current Linux Kernel Fedora Top First time here? Where did you add that? Please note that the version must match the running kernel.
Top TSU2 Posts: 3 Joined: 2013/12/30 21:20:59 Re: CentOS 6.2: VirtualBox Guest Additions -> Error: unable Postby TSU2 » 2013/12/30 21:49:55 Hello,I found this year old post but assume that it Top gerald_clark Posts: 10595 Joined: 2005/08/05 15:19:54 Location: Northern Illinois, USA Re: CentOS 6.2: VirtualBox Guest Additions -> Error: unable to find the sources ... Unable To Find The Sources Of Your Current Linux Kernel Virtualbox Guest Additions Learn More Red Hat Product Security Center Engage with our Red Hat Product Security team, access security updates, and ensure your environments are not exposed to any known security vulnerabilities. Unable To Find The Sources Of Your Current Linux Kernel Centos VMWare tools then got installed.
share|improve this answer answered Oct 23 '15 at 2:03 user513000 1 add a comment| up vote 0 down vote The error means that vboxdrv/vboxadd can't find your kernel sources. this contact form Specify KERN_DIR=
Has Darth Vader ever been exposed to the vacuum of space? Reply Trackbacks Virtualbox: Guest Additions: Makefile.include.header:106: *** Error: KERN_DIR does not point to a directory | Ora World says: December 18, 2014 at 11:36 am […] I was trying to install Except that I didn't have to install make or patch, just gcc. [[email protected] ~]# lsmod | grep -i vbox vboxsf 37535 0 vboxguest 284665 6 vboxsf vboxvideo 2148 1 drm 280012 have a peek here Messages emitted during module compilation will be logged to /var/log/vbox-install.log.
you can check this one: computingforgeeks.com/2015/08/… –realhu Jan 7 at 8:39 add a comment| up vote 17 down vote How to fix this but for Fedora First make sure that your Kern_dir Does Not Point To A Directory Check out the FAQ! Of course, I'm sure the correct source has been installed (I understand that in CentOS, there isn't a source package that matches every kernel, you only need to install kernel-devel for
Postby gerald_clark » 2012/05/18 17:23:26 Your booted kernel and the kernel-devel are not the same version! Unfortunately, this does not help. If you have any questions, please contact customer service. Check This Out Use the 30 daily voting points that you get!
Got these instructions from VirtualBox's website for Linux which seems to be down at the moment but the link is https://www.virtualbox.org/wiki/Linux_Downloads share|improve this answer edited Nov 3 '12 at 23:22 answered Board index The team • Delete all board cookies • All times are UTC + 1 hour [ DST ] Get VirtualBox Forum powered by phpBB © phpBB Group By any If looking at /var/log/bvox-add-install.log there are still alot of errors in the log. Makefile:192: Error: KERN_DIR does not point to a directory.
Reviewed the shell install script, and found that it sets KERN_DIR to /usr/src/kernels. Problem : unable to find the sources of your current Linux kernel Without above three packages you will get the following error message during the installation process. Running into the same issue, ran kernel-devel-$(uname -r), worked like a charm. Pro 764 points 6 July 2015 12:50 AM Christopher Miller The kernel that I have installed is the following: 2.6.32-431.e16.x86_64 I've also installed the following rpms: kernel-devel-2.6.32-431.el6.x86_64.rpm kernel-headers-2.6.32-431.el6.x86_64.rpm I uninstalled Guest
Its working now, and going forward I kind of know what to look for or troubleshoot if I have to do a fresh install or new install if the kernel is never trust a toad...::Grateful ArchDonor::::Grateful Wikipedia Donor:: Offline #4 2009-12-31 08:24:18 na12 Member From: /home/serbia Registered: 2008-12-23 Posts: 749 Re: [SOLVED] Can't build vboxdrv module toad wrote:Install the headers for kernel Specify KERN_DIR=
and confirmed the kernel mismatch. I feel that to get this installed is a type of hodge-podge of directions.