How-to Install VMware Player / Workstation on 2.6.24 Kernel

Update: If you are looking for patching VMware for Linux 2.6.25 Kernel – check here

Currently latest VMware Player and Workstation do not install under Linux 2.6.24 Kernel. This is a short how-to resolve the gcc/make errors that arise while configuring (

1. Download the latest vmware player (workstation) – currently VMware Player 2.0.2 Build 59824
url: – Read the Eula before downloading

2. tar xzvf VMware-player-2.0.2-59824.i386.tar.gz

3. cd vmware-player-distrib/

4. ./ – Proceed as usual when asked to run answer NO

5. Download the latest any-any patch – currently vmware-any-any-update-116
url: http://vm…

6. tar xzvf vmware-any-any-update-116.tgz

7. cd vmware-any-any-update116

8. ./ and when asked to run answer YES

9. Configure as usual

10. Enjoy!

PS. Link is broken so I reuploaded on my hosting. Patch is presented as is and I don’t take any responsibility for it. All credits go to the author.


114 Replies to “How-to Install VMware Player / Workstation on 2.6.24 Kernel”

  1. Works fine:
    – Kernel 2.6.24 (+ tuxonice patch)
    – Debian lenny/testing distro.
    – VMWare workstation 6.02

  2. Wow it works. was looking to make it run on debian and it does ;-)

    Sys specs kernel: on debian testing/unstable

  3. How about VMWare Fusion/OSX? The various threads I’ve found don’t address the version of vmware-tools included with Fusion. Dunno why Fusion has to have different tools…

  4. I’m running Hardy alpha 5 (2.6.24-11 generic)
    The tip works, but only if g++ is installed.
    When trying to run VMWare (Server 1.04) I then had problems like this:
    /usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/ no version information available (required by /usr/lib/
    /usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/ version `GCC_4.2.0′ not found (required by /usr/lib/

    So I ran these commands:
    cd /usr/lib/vmware/lib/
    sudo mv
    sudo ln -sf /usr/lib/
    cd /usr/lib/vmware/lib/
    sudo mv
    sudo ln -sf /lib/
    (hope that’s clear…)

    Now it seems to be OK.

  5. Hi Peter. I have to say thank you for this great work !!
    The configuration of VMware Workstation 6.0.0 build-45731 for Linux for this
    running kernel completed successfully.
    I’m running

  6. Fedora 8

    Still getting errors after running any-any-update?
    Try: yum install gcc-c++

    Worked for me :)

  7. To [daveStyle]:
    it’s true.
    Install gcc-c++ if you get:
    make[1]: Entering directory `/usr/src/kernels/′
    CC [M] /tmp/vmware-config3/vmmon-only/linux/driver.o
    CC [M] /tmp/vmware-config3/vmmon-only/linux/driverLog.o
    CC [M] /tmp/vmware-config3/vmmon-only/linux/hostif.o
    CC [M] /tmp/vmware-config3/vmmon-only/common/comport.o
    CC [M] /tmp/vmware-config3/vmmon-only/common/cpuid.o
    CC [M] /tmp/vmware-config3/vmmon-only/common/hash.o
    CC [M] /tmp/vmware-config3/vmmon-only/common/memtrack.o
    CC [M] /tmp/vmware-config3/vmmon-only/common/phystrack.o
    CC [M] /tmp/vmware-config3/vmmon-only/common/task.o
    gcc: error trying to exec ‘cc1plus’: execvp: No such file or directory
    make[2]: *** [/tmp/vmware-config3/vmmon-only/common/task.o] Error 1
    make[1]: *** [_module_/tmp/vmware-config3/vmmon-only] Error 2
    make[1]: Leaving directory `/usr/src/kernels/′
    make: *** [vmmon.ko] Error 2
    make: Leaving directory `/tmp/vmware-config3/vmmon-only’
    Unable to build the vmmon module.

  8. latest vmware server 1.0.5 plus only:

    Compiles ok with warnings:

    CC [M] /tmp/vmware-config5/vmmon-only/common/task.o
    cc1plus: warning: command line option “-Werror-implicit-function-declaration” is valid for C/ObjC but not for C++
    cc1plus: warning: command line option “-Wdeclaration-after-statement” is valid for C/ObjC but not for C++
    cc1plus: warning: command line option “-Wno-pointer-sign” is valid for C/ObjC but not for C++
    cc1plus: warning: command line option “-Wstrict-prototypes” is valid for Ada/C/ObjC but not for C++
    /tmp/vmware-config5/vmmon-only/common/task_compat.h: In function ‘void Task_Switch_V45(VMDriver*, Vcpuid)’:
    /tmp/vmware-config5/vmmon-only/common/task_compat.h:2666: warning:
    ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in
    this function
    /tmp/vmware-config5/vmmon-only/common/task_compat.h:2666: warning:
    ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this
    /tmp/vmware-config5/vmmon-only/common/task_compat.h:2666: warning:
    ‘sysenterState.SysenterStateV45::rsp’ may be used uninitialized in this
    /tmp/vmware-config5/vmmon-only/common/task_compat.h:2666: warning:
    ‘sysenterState.SysenterStateV45::rip’ may be used uninitialized in this

    All fine except bridge networking does not work. No errors logged in syslog or vmware.log.

    Where to start looking?

  9. I’m using Ubuntu 8.04 alpha with kernel 2.6.24-12-generic

    After the any-any patch, I’m able to compile the VMware modules, but when I try to open a virtual machine, I get the following error:

    Version mismatch with vmmon module: expecting 161.0, got 137.0.
    You have an incorrect version of the `vmmon’ kernel module.
    Try reinstalling VMware Workstation.

  10. @Daniel Serodio

    Probably you are using old version of VMware Workstation. You can try downloading the latest version from the site.

    If the problem persists please drop me a line

  11. An update to my earlier post. Oops, guess what I missed in the logs:

    bridge-wlan0: enabling the bridge
    bridge-wlan0: is a Wireless Adapter
    vmnet: You are trying to use wireless bridged networking together with
    vmnet: vmware-any-any-update. This is not supported configuration, and
    vmnet: your wireless bridge will probably not work.
    bridge-wlan0: up
    bridge-wlan0: already up
    bridge-wlan0: attached

    Which all makes sense for a server product. bridge-eth0 works just fine – yippee.

    So I have vmware server 1.0.5 working on Debian’s 2.6.24-1-amd64. This is likely to be the the kernel in the Debian release so this is good news. Please can I join Mr Pfeiffer in saying a BIG THANKS!

  12. @Peter, I uninstalled VMware, installed VMware Workstation 6.0.3 build-80004 with the any-any 116 patch and still get the same error… :-/

  13. ubuntu hardy beta

    patch didn’t seem to work as it was still complaining about cc1plus –

    apt-get install build-essential

    and it compiled fine. Thanks for the hints guys, installing build-essential installed g++ and g++4.2.

  14. vmware-any-any-update-116.tgz doesn’t work with VMware-workstation-6.0.3-80004, it’s expecting 167.0 of the module and is getting 137.0. I guess this doesn’t actually patch the modules as they’re distributed with VMware, it replaces them with older versions that have been patched to work?

  15. After unpacking lib/vmware/modules/source/vmmon.tar and changing “asm/bitops.h” to “include/bitops.h” in vmmon-only/include/vcpuset.h, the vmmon module compiles fine. There are no other errors with the remaining modules on

  16. Mike is on the right track, but the correct include is “linux/bitops.h” not “include/bitops.h”.

  17. sorry, doesnt work for me…i googled and always found the same sollution. i use debian etch and kernel tried it with all the different any-to-any patches but still get this fault:

    make[2]: *** [/tmp/vmware-config8/vmmon-only/linux/driver.o] Fehler 1
    make[1]: *** [_module_/tmp/vmware-config8/vmmon-only] Error 2
    make[1]: Leaving directory `/usr/src/linux-headers-’
    make: *** [vmmon.ko] Fehler 2
    make: Leaving directory `/tmp/vmware-config8/vmmon-only’
    Unable to build the vmmon module.

    the path to the kernel-headers is definitly correct…

  18. @alex

    Could you please post more info – Vmware player, workstation or server are you using. Did you compiled this kernel or it is backport? What version of GCC do you use?

    I’m sure if I can not help you there is someone who will


  19. Thanks a lot.
    Im running debian lenny/sid 2.6.24-1-686 and vmware server1 .0.4 build-56528.

    I couldn’t compile vmmon module when i updated my kernel and i downloaded the patch. After unsucessfull compiling, I tried to apply the patch and an error told me that the files required to patch did not exist.

    This was because a failed deletes some files (or every file) of your vmware install. After skipping this comprobation i could patch and my vmware is now running, with my old configuration perfectly working (at least for now).

  20. thanks,
    work on Ubuntu Hardy 8.0.4 beta
    apt-get install build-essential
    then installed as above

  21. It does not work on FC8 – VMWare Player 2.0.3 (VMwareTools-6.0.3-80004)

    1) gives the following error while building vmhgfs module

    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-config4/vmhgfs-only’
    make -C /lib/modules/ SUBDIRS=$PWD SRCROOT=$PWD/. modules
    make[1]: Entering directory `/usr/src/kernels/′
    CC [M] /tmp/vmware-config4/vmhgfs-only/backdoor.o
    CC [M] /tmp/vmware-config4/vmhgfs-only/backdoorGcc32.o
    CC [M] /tmp/vmware-config4/vmhgfs-only/bdhandler.o
    CC [M] /tmp/vmware-config4/vmhgfs-only/cpName.o
    In file included from include/linux/string.h:11,
    from /tmp/vmware-config4/vmhgfs-only/cpName.h:18,
    from /tmp/vmware-config4/vmhgfs-only/cpName.c:18:
    include/linux/types.h:40: error: conflicting types for ‘uintptr_t’
    /tmp/vmware-config4/vmhgfs-only/vm_basic_types.h:170: error: previous declaration of ‘uintptr_t’ was here
    make[2]: *** [/tmp/vmware-config4/vmhgfs-only/cpName.o] Error 1
    make[1]: *** [_module_/tmp/vmware-config4/vmhgfs-only] Error 2
    make[1]: Leaving directory `/usr/src/kernels/′
    make: *** [vmhgfs.ko] Error 2
    make: Leaving directory `/tmp/vmware-config4/vmhgfs-only’
    Unable to build the vmhgfs module.

    2) cut & paste between host (Win XP) and guest (FC8) still does not work

  22. FC8 & Kernel- & vmware workstation 5.5.6

    Base install (with KDE instead of Gnome) required the installation of the following packages:


    Without the last package the any-any patch will exit with an error.

    Thanks for the info!

  23. Thanks a lot, it works correctly.
    To all – to be attention it works correctly only if you do:
    1 – ./ – Proceed as usual when asked to run answer NO
    2 – ./ and when asked to run answer YES
    If you ready have VmWare and updated Kernel to 2.6.24 you must to do installing from 1st step, not use vmware-any-any before you don’t reinstall vmwares’s system files from distrib.

  24. @Daniel Serodio

    i have met the same problem with you,but i reconfig the vmware,everthing is ok,i don’t know how can this happen

  25. This does not work for VMware server 1.0.5 and kernel
    VMware server cannot be contacted afterwards, and the virtual machines does not have any network connection.

  26. At least on Debian Unstable with linux-image-2.6.24-1-686 (2.6.24-5) I’m successfully running VMware Server 1.0.5 build-80187. Please post more information for your distribution, kernel, etc.

  27. I apologize in advance as I have not been on linux in awhile..

    After I try step

    sudo ./

    I am getting

    unable to open the installer database /etc/vmware/locations

    my thinking was maybe to move the patch to say /opt/local or something similar and try it again as a work around..doe stha tsound right..thanks

  28. @shareme

    Did all previous steps completed successfully?
    Also if the message is “Unable to open the installer database /etc/vmware/locations in read mode” try googling because there are plenty of users describing the same issue.

    Also I suggest to be root all the time (during install) instead of using sudus

Comments are closed.