Skip to main content

Missing Kernel Headers with VMware Tools Install on Kali Linux 2.0

So, the case of the missing kernel headers continues with installing VMware Tools on Kali 2.0... As some of you may know, this issue was seen with Kali 1.0.5 when using it as a virtual machine on VMPlayer. Thankfully the fix is fairly easy. The specific error you might see is:
Searching for a valid kernel header path...
The path "" is not a valid path to the 4.0.0-kali1-amd64 kernel headers.
Would you like to change it? [yes] 
Or, if you're like me and just press enter:
The path "" is not a valid path to the 4.0.0-kali1-amd64 kernel headers.
Would you like to change it? [yes] 
Okay, so let's get this fixed. My experience was similar to what was done in version 1.0.5, but with a small modification form what was done with the previous version (Titan Tech documented what to do in the previous version HERE). Here's what happened with me.

Exit out of the install of VMware Tools and hammer through the following commands:
echo cups enabled >> /usr/sbin/update-rc.d
echo vmware-tools enabled >> /usr/sbin/update-rc.d
apt-get install gcc make linux-headers-$(uname -r)
ln -s /usr/src/linux-headers-$(uname -r)-amd64/include/generated/uapi/linux/version.h /usr/src/linux-headers-$(uname -r)-common/include/linux/

Now, from here go back to the install of VMware Tools, and everything should go off without issue.

For those that haven't installed VMware Tools before. After mounting the VMware Tools file, I typically use the File Browser to copy the tar ball to /tmp and run the following commands in the terminal:
cd /tmp
tar -zxvf VMwareTools-*.tar.gz
sudo ./vmware-install.p
References
http://titantechcorp.com/?p=834
https://www.vmware.com/support/ws55/doc/ws_newguest_tools_linux.html

Comments

Popular posts from this blog

Using Python for GPG/PGP File Encryption - Part 1

So, this will be the start of a series that will build a python script for GPG/PGP file encryption. In this post, we'll look at installing gnupg for python and using python to setup the keystore, create a private key, exporting the associated public key, and importing a public key. Now everything done here can be done with simple gnupg commands, but learning how to do this with python will help in understanding the script we'll be building to complete file encryption. I will be covering non-python gnupg commands in a future post. Additionally, the folks at the python-gnupg site over at pythonhosted.org have done a really great job at documenting everything (link to their site at the bottom). The stuff I'll be going over will be more of a start-to-finish for anyone that may get lost in the muck of doing stuff with python. Full Disclosure #1: Any key identifier throughout the series of posts is FICTITIOUS and DOES NOT represent any real key, either associated with myself or...

Windows Server 2008: Log on as batch job

From time to time, I have to set up some scheduled tasks that required a dedicated account to run. And when doing so, I'll usually forget that the dedicated account usually isn't given any more permissions than what it needs to complete the task at hand. So, after setting up the task, Windows will usually yell at me and say "The account needs batch job rights". So here's how to grant batch job permissions on your server. Go to your start menu, and start searching for Local Security Policy In the left pane of the MMC that opens up, expand Local Policies, and highlight User Rights Assignment. Now, in the left right pane, locate "Log on as a batch job" and double click it. In the properties window that opens up, add the user or group that needs this permission. I find that if you have multiple service accounts running different tasks on the same server, it's easier to just add a group verses the individual a...

Replacing rsyslog with syslog-ng on RHEL 6.5

So...I had a piece of monitoring software that didn't play nice with the RHEL default rsyslog for log collection. The software was developed to only work with syslog-ng. I'll be going over the steps that I took, that worked for me, in replacing rsyslog with syslog-ng. I would imagine that these same steps should work for any Linux system similar to RHEL (Fedora, CentOS, etc.). For others (like Debein based distributions), I would need to look into that (coming in a future update to this post). First, remove rsyslog. You will need to keep the dependencies as they will be needed for syslog-ng: sudo rpm -e --nodeps rsyslog Next we will need to add the EPEL repository (more info can be found HERE ): wget http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm sudo rpm -ivh epel-release-6-8.rpm sudo yum repolist That last command will list all the installed repositories. You are simply verifying that the EPEL package has been installed. Now that we fi...