Posted in Computers, Fedora, Linux

VMware Tools Cannot Find Kernel-Headers on Fedora 18 x64

I recently installed Fedora 18 x64 on VMware Workstation 9, and was unable to initially complete the VMware Tools installation using the same methods that I’d previously done many, many times with prior Fedora installations. The installer kept telling me that it couldn’t find the kernel-headers folder. I had installed the development tools with my Fedora install, and they were all up to date, so I was a bit puzzled.

Prior to installing the VMware Tools, you need to install the Fedora development tools if you don’t have them – or if you’re unsure, just check – otherwise the installer will complain that it cannot find something, and will ask you to provide a path.

The development tools needed are: gcc, make, binutils, kernel-devel, kernel-headers

I also recommend updating the existing kernel to match the versions from kernel-devel and kernel-headers.

  1. Update your kernel, restart the vm after the installation: # yum update kernel
  2. Install the development tools, restart the vm when finished: # yum install gcc make binutils kernel-devel kernel-headers
  3. Run the ./vmware-install.pl script, accepting all the defaults (unless you know what you’re doing and want or need to change something)

If the script complains that it cannot find the location of the kernel-headers – and you verify that they are installed by typing # rpm  -qa, then you must copy the kernel-headers from one location to another. Find out which kernel you’re using with # uname -a. The current kernel on my system as of 01-19-2013 is 3.7.2-201.fc18.x86_64

Run the following command to copy the folder from one location to another location, which is where the installer is looking for those header files.

# cp /usr/src/kernels/3.7.2-201.fc18.x86_64/include/generated/uapi/linux/version.h /lib/modules/3.7.2-201.fc18.x86_64/build/include/linux/

If you’re running the script, you can type that path into the installer where it asks for the header-files location. If you’re not running the installer script, run it again, and it should find the path automatically.

Thanks to user jgkirk from the VMware forums for this tip. The original post that helped me can be found here.