VMware workstation kernel issue on Fedora 17

After updating my Fedora 17 yesterday I had a minor issue... something that should have been solved ages ago by VMware. It is no fun to launch your paid software and find out that the software isn't working properly.

After launching VMware workstation 9.0.1 I got the message:



I new that I had updated the kernel and I always take care that I also install the kernel-headers so what is this?

So it is time for autopsy - crank up the almighty terminal:

teemu@np530 ~$ sudo yum install kernel-headers
.....
Package kernel-headers-3.7.9-101.fc17.x86_64 already installed and latest version
Nothing to do


OK, the version is correct (this is important!) - where is it? Where is it exactly located? What's the fuss?

teemu@np530 ~$ uname -r
3.7.9-101.fc17.x86_64
teemu@np530 ~$ rpm -ql kernel-headers-$(uname -r)|grep version.h
/usr/include/linux/dvb/version.h
/usr/include/linux/version.h

Everything OK - lets type in the path /usr/include/linux/ to the pop-up window
No luck. Software doesn't accept given location.
Hammer... Oops.... Google time: vmware workstation kernel-header default location?

Quick'n'dirty solution is just to create a copy

teemu@np530 ~$ sudo cp /usr/include/linux/version.h /lib/modules/$(uname -r)/build/include/linux/

Better way, if there is one, to solve this is to create a symlink with ln -s


teemu@np530 ~$ ln -s /usr/include/linux/version.h /lib/modules/$(uname -r)/build/include/linux/version.h


So back to VMware workstation pop-up window - click on Cancel button, relaunch the VMware workstation and you get a different kind of welcome message:




Just click Install and that's it.
Honestly quite disappointing; I remember battling with this issue earlier and kind of astonished that it still exists(!)

Notice!


It appears that the instructions above does not work all the way with latest Kernel 3.8.x versions (you can check with terminal command uname -r)

If you fixed the kernel header issue as stated above you should get vmci error (on the screen check window and listed in the logs) during the re-start of vmware workstation.

There is a thread about this issue on vmware community.

The bottom line: forget the patch files available on the community pages and just go and get the free maintenance release 9.0.2 update (whopping 400Mb, sigh).
As you can't most likely get the vmware started you need to install this maintenance release manually -  donwload the 9.0.2 release followed by following terminal magic:
cd Downloads
chmod +x VMware-Workstation-Full-9.0.2-1031769.x86_64.txt
sudo ./VMware-Workstation-Full-9.0.2-1031769.x86_64.txt 
There is no need to backup the virtual machines or configuration - the installer understands automatically that this is an update.

Getting a wee bit bored of constant fixing....




Comments

Post a Comment