VMware Player 5.0.2, Ubuntu 13.04, kernel 3.8.0 patch

vmware_compAfter upgrading my kernel to 3.8.0-6-generic on Ubuntu Raring today vmplayer 5.0.1-894247.x86_64 was not able to find the C header files matching the latest kernel on first run. It was throwing the following error:

C header files matching your running kernel were not found. Refer 
to your distribution's documentation for installation instructions.

Evidently the installation process is unable to find the correct version.h file. I used:

ln -s /usr/src/linux-headers-3.8.0-6-generic/include/generated/uapi/linux/version.h \

It continued for a while but eventually failed to compile all the modules. Then I found the required patch to complete the compilation in vmware community forums. To apply the patch:

cd /usr/lib/vmware/modules/source
tar -xf vmci.tar
cd vmci-only
patch -p1 < 'patchfile'
cd ..
tar -cf vmci.tar vmci-only/

then re-run vmware installer.
In case VMware is asking for your preferences on every run, you probably need to create the preferences file manually:

mkdir .vmware
touch .vmware/preferences
chmod  777 .vmware
chmod 666 .vmware/preferences

If you face any issues while compiling the kernel modules you can also try compiling them from the terminal using:

vmware-modconfig --console --install-all


  1. I tried installing the latest VMware Player 5.0.2 on the same setup. It uninstalled the previous version and installed itself without any issues. The procedure works fine on Ubuntu mainline kernel 3.9.0 and 3.9.7 as well.
  2. VMware Player 6.0.0 has been released on Sep 3, 2013. I have installed it on kernel 3.11.0 and 3.12.0 from Ubuntu mainline kernel PPA without any issues.

12 thoughts on “VMware Player 5.0.2, Ubuntu 13.04, kernel 3.8.0 patch”

    1. Probably you need to install the Linux header packages. Install linux-header-xxx and linux-header-xxx-generic from synaptic.

  1. Hello Arun,
    i run in the same problem with ubuntu 13.04 after a kernel update to the kernel 3.8.0-29-generic.
    First i made the symbolic links.
    Then the patch file was not working because of different line numbers, so i changed it manually in the vmci-only/linux/driver.c
    Because i didnt know to change the patch file:
    Here my solution:
    cd /usr/lib/vmware/modules/source
    tar -xf vmci.tar
    cd vmci-only
    now i changed manually the line 127:
    from .remove = __devexit_p(vmci_remove_device),
    to .remove = vmci_remove_device,

    the same i did in the line 1753:
    from static int __devinit
    to static int

    the same i did in the line 1981:
    from static int __devinit
    to static int

    than recreate the tar-file:
    tar -cf vmci.tar vmci-only/
    and run:
    sudo vmware-modconfig –console –install-all
    i could imagine this would be helpful to someone else.
    i think if someone can change the patchfile would be easier.
    regards Martin L.

  2. Thank you, i had the same problem with 3.8.0-7, so i followed your links and everythink works great now!

  3. Hi Arun
    Thanks for the reply.
    Just for the records, after reading
    2013-02-23T16:46:36.858+01:00| vthread-3| I120: Extracting the vmci source from “/usr/lib/vmware/modules/source/vmci.tar”.
    2013-02-23T16:46:36.866+01:00| vthread-3| I120: Successfully extracted the vmci source.
    I learnt that omitting command tar -cf vmci.tar vmci-only/ as found in http://communities.vmware.com/message/2182440#2182440 was not a good idea.
    I can confirm that the instruction above work for kernel version 3.8.0-7-generic.

  4. Hmm, link seems to be fine, but patch did not work here:
    Linux xxxxxx 3.8.0-7-generic #15-Ubuntu SMP Thu Feb 21 20:07:18 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
    VMware Player 5.0.1 build-894247

    To sum up: I am not able to run VMware Player 5.01 on 13.04 usind kernel 3.8.0-7


Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s