Apr 012012

NOTICE: This patch works fine with 3.5.0 and 3.6.0-rc1

UPDATE: kwasik updated the previous 7.1.x/3.1.x patch with the changes detailed here and made a new patch so if you are using that version of vmware you can grab it ready from here

Another version of the kernel another broken module…

This time it was something easier and with a short solution directly in the kernel documentation, but not much said about the reasons for the change (which was done 11 days ago) except that it fixed bugs caused by misuse.

Anyway d_alloc_rot was replaced with d_make_root as said here. So that’s practically the fix to apply to the sources in order to make vmblock build (even though vmware seems to start also with this module not running).

The patch should be easy to apply also for 7.1.x vmware modules (but I’m not providing a patch as I don’t have the sources anymore).

This is the procedure:

Open vmblock.tar and search for filesystem.c. Then there search for d_alloc_root(rootInode). That needs to be replaced with d_make_root(rootInode). This will make vmblock build successfully.

And here it is the easier way for 8.0.x/4.0.x users: vmware 8.0.2 fix for linux 3.4.0

Remember that if you apply the patch you’ve to always start with clean module sources from 8.0.2 release. Also be careful that vmware, when uninstalled, doesn’t clean entirely it’s modules folder, so remember to do so before reinstalling it.

Attached Files:

  92 Responses to “vmware workstation 8.0.2/player 4.0.2 (and 7.1.x/3.1.x) fix for linux kernel 3.4.0”

  1. Thanks once again for doing all the hard work, and keeping VMware and NVIDIA in line with the latest Kernel quirks..

    Best regards,

    Robert Gadsdon

  2. Works for Player 4.0.3 — just had to update versoin check in the script :)

  3. Thanks, this worked fine on version 8.0.3 of Workstation. I just changed vmreqver to 8.0.3. in the patch script.

    Your scripts make my life much much easier, and I really appreciate them!

  4. Just tested with 4.0.3. After changing the version in the script, it patches just fine. You should update your script.

    Thanks a lot.

  5. i too, only change version and works with 8.0.3, and works on kernel 3.3.4. (3.3.0-trunk-amd64 debian)

  6. I couldn’t get it past the version check with the latest VMware Player, so commented out the error check in line 29 of the script. Now it works!


    • I also had to comment out the error check. For the version. Even though i edited the vmreqver upon exec ,i recieved Sorry, this script is only for VMWare WorkStation 8.0.3 or VMWare Player 4.0.2.
      This was a fresh 12.04 and fresh 8.0.3 install.

      For Notes: I believe I installed 8.0.3 before I had completed/restarted after doing a post-install apt-get update. However, the exec of the script was post reboot. I did not re-run the bundle afterwards.

    • Thanks. It worked after commenting. :)

  7. Many thanks !

    • I applied the patch for kernel 3.2 for vmplpayer 4.0.3 (had to change version first) succesfully.
      Applying the patch for kernel 3.4RC6 I get a “you already applied this patch” message.

      When I start vmplayer from kernel 3.4 It tells me this:
      Your kernel was compiled with gcc version 4.4.3 while the version located is 4.6. Compiling kernel modules with this version is not recommended.

      Any suggestions?

      • you don’t need to reapply the patch if it’s the proper one, if it’s not you’ve to start from scratch using a clean modules source folder.
        You should ask your distribution and if you’ve multiple versions of gcc use the right one

  8. I’ve run into an issue when attempting to apply the patch to a fresh install of Player 4.0.3. When the player installs, it tries to compile the modules. This will, of course, fail for the most part; however, vmmon will compile and load. Trying to run the script at this point results in an error because vmmon.ko won’t unload.

    After stumbling around a bit, I discovered that deleting this module, rebooting, and running the script (after fixing the version number, of course) results in a successful build.

    I’ve documented a step-by-step here: http://www.kubuntuforums.net/showthread.php?58830&p=298479&viewfull=1#post298479

    • Very helpful comment (to check kernel modules). I could not get the “8.0.2-on-3.4″ patch to work on VMware Workstation 8.0.4 running on 3.4.6-1.fc16.i686.PAE until I realized that vmmon was loaded before I had the chance to patch the source, and wasn’t properly unloading.

      The symptom was I could get the VMs to start no problem, but no network connection (using bridge mode).

      I didn’t have to reboot, but I did have to:

      0) Upgrade kernel to above (3.4.6) version
      1) After completely uninstalling 8.0.2 workstation, uninstall vmnet and vmmon kernel modules:
      # modprobe -r vmnet vmmon
      2) Install 8.0.4:
      # bash VMware-Workstation-Full-8.0.4-744019.i386.bundle
      3) Unload vmmon kernel module (again!)
      # modprobe -r vmmon
      4) Edit “patch-modules_3.4.0.sh” and replace 8.0.2 with 8.0.4
      5) Run “patch-modules_3.4.0.sh”
      6) The vmware service appears to fail, but doesn’t(?!), and this time the vmnet interface is visible in my ifconfig output (it wasn’t when step 3 was ommitted)
      7) start vmware


  9. greatly appreciated!!

  10. [...] = d_alloc_root(ip); #endif So following a suggestion made in relation to a similar problem in vmware workstation 8.0.2 7.1.5 / player 4.0.2 3.1.5 fixes for linux 3.4 | Weltall's blog I commented out the line referring to d_alloc_root and replaced it by the one using d_make_root [...]

  11. Worked like a charm. Thank you a LOT!
    Fedora 17 with Kernel 3.4. vmplayer 4.0.3

  12. Wonderful, it worked without problem … very many thanks!

  13. i’m trying to run workstation 7.1.5 under x86_64 FC 17 (kernel 3.4). i realize there isn’t a patch for it but your comments suggest it could be done manually? looking for any suggestions/pointers?


    • start with the 3.2 patch and add those 4 lines (or 1 line change for a quick patch) which can be seen in the latest patch

  14. Thanks for your work! After reading your advices for workstation 8.0.2/player 4.0.2 i have made little fixes to your script/patch that now works on workstation 7.1.6/player 3.1.6 for kernel 3.4.0 ( 3.4.0-1.fc17.x86_64). As you see i’m using 64 bit Fedora 17. If you’d like i can send script with patch to attach to this blog post for folks who are stuck to 7.1.x workstation like me :-)
    Thanks again !

  15. Appears to work on Fedora 17, 3.4.0-1.fc17.x86_64 with VM Workstation 8.0.4.

  16. Thanks for the update.

    Seems to work fine with latest vmware player 4.0.4 also, by changing the version number in the script.

    Also I upgraded from a previous version that was already patched and gave me an error:

    /usr/lib/vmware/modules/source/.patched found. You have already patched your sources. Exiting

    I just removed the above touch file and ran it again which worked.

    Thanks again.

  17. [...] it won't help you much, but VirtualBox works just fine on Beta1. Nope. -But- we found a fix at: vmware workstation 8.0.2 7.1.5 / player 4.0.2 3.1.5 fixes for linux 3.4 | Weltall's blog Using the info from there plus previous experiences and we got VMware version 8.0.3 working on [...]

  18. How exactly and where exactly do you change the version number in the script?

  19. [...] quelques recherches, voici la page qui résout le soucis. Merci LE-NET :-) This entry was posted in Informatique, RedHat. Bookmark the permalink. [...]

  20. Thank you, this still works in WS 8.04

  21. Thank you very much, I can confirm this is working with ’3.4.3-1.fc17.x86_64′ (Fedora 17) and WS 8.0.4.

    Your work here is very much appreciated.


  22. Hey weltall i love you in the most heterosexual way!

    My english y very very bad, but i want to thank you.
    Your work help people around the world that they haven’t no idea about the script whato to do.

    I can confirm too this is working with “3.4.3-1.fc17.x86_64″ (fedora 17 x64) and VMWare worstation (and player) 8.0.3
    I just changed vmreqver to 8.0.3. in the patch script. (like bob).
    Thanks, Orange.

  23. I’m having issues on Fedora x86_64 running Kernel 3.4.2-1 .

    I’ve uninstalled vmplayer and tried reinstalling the patches but things are still failing:

    tmp/vmware-root/modules/vmci-only/linux/driver.c: In function ‘__check_disable_host’:
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:2498:1: warning: return from incompatible pointer type [enabled by default]
    (and line 2501, 2504, and 2507 in driver.c)

    • that’s only a warning, it won’t stop compilation.

      • But it does appear to be failing on startup. I’ll try again.

      • Nope. I just reinstalled/repatched and got this:

        /tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:528:15: warning: assignment makes pointer from integer without a cast [enabled by default]
        cc1: some warnings being treated as errors
        make[2]: *** [/tmp/vmware-root/modules/vmblock-only/linux/filesystem.o] Error 1

  24. I figured the problem.
    This is the default line:

    This line 528 in vmblock-only/linux/filesystem.c

    The original (not valid in Kernels 3.4 or later
    rootDentry = d_alloc_root(rootInode);

    Change it to:
    rootDentry = d_make_root(rootInode);

    It worked fine after this.

  25. Worked for me on fc17 with the 3.4.4-5.fc17.x86_64 kernel, thank you!!!

    I downloaded (see above) the patch (vmware802fixlinux340.tar.gz) and edited it (see below). After installing the kernel-devel-`uname -r` and patch RPMs it worked like a charm.

    [root@laptop ~]# uname -r

    [root@laptop ~]# diff patch-modules_3.4.0.sh patch-modules_3.4.4.sh
    < fpatch=vmware3.4.0.patch
    > vmreqver=8.0.4

    [root@laptop ~]# diff vmware3.4.0.patch vmware3.4.4.patch

  26. Man… you’re a life saver – thanks again!

    I’ve lost count how many times this post saved my skin

  27. works for VMPlayer 4.0.4

  28. its work for vmware 8.0.4 x64 in kernel 3.4.4-5.fc17.x86_64, i change 8.0.2 to 8.0.4 in script, thanks

  29. Thanks a lot,
    works with player 4.0.4 and kernel 3.4.4

  30. Attempting to run the 7.1.6 patch after install just gives me the
    patch-modules_3.4.0.sh: 27: [: workstation7.1.6: unexpected operator
    patch-modules_3.4.0.sh: 28: [: workstation7.1.6: unexpected operator
    Sorry, this script is only for VMWare WorkStation 7.1.6 or VMWare Player 3.1.6. Exiting

    And I have no idea why, seeing as I installed it 30 seconds before trying to run the patch. Any ideas?

  31. You Sir, are a legend! Without your efforts, I would have been proper foobar’d. Thank you a thousand times!

  32. Also worked with Vmware Workstation 8.04 on kernel 3.4.6:

    changed the two lines in the file patch-modules_3.2.0.sh (from .2 to .4)


    Works perfectly! Thanks so much!

  33. Works like a charm also for Kernel 3.4.6-1 and VMWare Player 4.0.4 !
    Just change the version in the script !

  34. I tried the patch vmware802fixlinux340 on fedora 17 kernel 3.4.6-2.fc17.i686, and vmplayer 4.0.2. When I ran the patch this was the output:

    patching file vmblock-only/linux/filesystem.c
    patching file vmnet-only/filter.c
    patching file vmnet-only/netif.c
    patching file vmnet-only/userif.c
    gcc and kernel headers must be installed

    All done, you can now run VMWare Player.
    Modules sources backup can be found in the ‘/usr/lib/vmware/modules/source-player4.0.2-2012-07-27-17:40:58-backup’ directory

    When I tried to run vmplayer again it gave the familiar error:
    “Before you can run VMware, several modules must be compiled and loaded into the running kernel…
    Kernel headers for version 3.4.6-2.fc17.i686 were not found…”

    I’m not sure what I’m missing here. Could it be that when I uninstalled vmplayer I did not do a good enough job of cleaning up the remaining files? What files should be removed? Or what else could I be missing?


  35. I ran the http://weltall.heliohost.org/wordpress/wp-content/uploads/2012/04/vmware716fixlinux340.tar.bz2 on fedora 16. It worked for 32 bit guests but Win7_64 bit guest will not start and I have to reboot my linux host each time.
    I’m using the patch for kernel 3.1 and it’s working perfectly.
    I’m wondering if a 64 bit guest can run on VMWare Workstation 8 using a 3.4 version of the kernel.


  36. [...] you find that your Workstation 8 or Player4.0.x doesn't work you might try this patch form here: vmware workstation 8.0.2 7.1.5 / player 4.0.2 3.1.5 fixes for linux 3.4 | Weltall's blog Look for And here it is an easier way for 8.0.x/4.0.x users That's where I got the patch for my [...]

  37. Hi, gentleman

    Any news about patch for 3.5?

  38. On Fedora 17 with kernel 3.5.0-2 and VMWare Workstation 8.0.4 I had to change 2 files – filesystem.c in vmhgfs.tar and also in vmblock.tar

    thanks for your help – this was driving me mad!

    • Hi,
      what did you change? please :) i have same problem. I’m using Fedora 17 with kernel 3.5.0. Thank you very much.

  39. Just installed Player 4.0.4 on Fedora 17 with your patch and it worked without a hitch! Thanks a lot for your work.

  40. [...] have updated the links and the instructions to work with the latest patch files. You can go to Weltall’s blog to read more about the process if you are [...]

  41. new version vmware 9 vmware-player 5 help?

    • … Are you serious… they still didn’t fix it… I’m really without words, anyway I’ll have a look at it.

  42. Great ! It works also on Fedora 17 with last kernel update 3.5.2-3.fc17.i686.
    VMware Wks 9 and Player 5 hung and reboot the PC when you try to start a Windows VM (XP Professional), despite the installation didn’t shown any problems.

  43. Wow. After searching for about 1-2 hours for possible fixes, I finally found it! I use VMWare Workstation for school mostly, and was having issues with it and my ArchLinux kernel. I simply edited the version in the file and it ran like a charm! Thank you very much for the work you’ve done in this, it fixed my biggest problem! (My school doesn’t upgrade versions very quick so I’ll be on 8 for a while, but judging from the comments there is another required fix for Workstation 9. Heh)

    Thanks again. Wonderful.

  44. Hi, the patch worked nicely on my brand new OpenSUSE 12.2 -> Kernel 3.4.6-2.10-desktop.

    Thank you very much !!!

  45. This saved my arse after a long-postponed upgrade to Fedora 16. Many, many thanks.

  46. I am very sorry, I uninstalled vmwareplayer, rebooted the notebook, exactly followed the instruction, downloading and extracting vmwareplayer and patch. In spide of doing this exactly I get the message: [: player3.1.6: unexpected operator
    Sorry, this script is only for VMWare WorkStation 7.1.6 or VMWare Player 3.1.6. Exiting

    Thanks for help

  47. Thank you so much, this is very helpful!

  48. Awesome work.

    Just want to let you all know, I noticed VMWare has a new 5.0 release which does work on the 3.4 kernel :)
    And I think they should hire you for it! ;)

  49. Hi Weltall,

    thanks for the good work – it saved my day. After Upgrading to openSuSE 12.2 my VMWare Workstation 8.0.3 didn’t compile anymore. After a short google search I found Your blog, read some of the comments, extracted the patch, changed the Line vmreqver to 8.0.3 and started the script as root.

    Voila. VMWare started without any problems.

    Thanks so much.

  50. I just updated the Fedora 17 kernel to and re-installed the patch. vmware service now fails to start. I hope this is an easy update to the patch.

    Thank you!

    • I don’t use fedora, you might want to post the logs or ask them to fix the patches so they are in line with vanilla kernels.

  51. Thanks a lot. It worked for 3.4.6 and vmware 8.0.4

  52. Works on Ubuntu 12.10 with Kernel 3.5.0-18-generic. VMWare workstation 8.0.4 and player 4.0.4 after modifying

    filesystem.c inside /usr/lib/vmware/modules/source/vmblock.tar

    to look like this (Line 528)

    And editing the patch file to match workstation and player versions.


  53. Hi, I am installing workstatrion 7.1.6 on Linux mint 13

    $ uname -a
    Linux m65 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:41:14 UTC 2012 i686 i686 i386 GNU/Linux

    When I run the patch, I get

    $ sudo ./patch-modules_3.4.0.sh

    make[2]: *** [/tmp/vmware-root/modules/vmblock-only/linux/filesystem.o] Error 1
    make[1]: *** [_module_/tmp/vmware-root/modules/vmblock-only] Error 2
    make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-23-generic’
    make: *** [vmblock.ko] Error 2
    make: Leaving directory `/tmp/vmware-root/modules/vmblock-only’
    Unable to install vmblock

    When I try to launch vmware, I get

    $ sudo vmware

    filename: /lib/modules/3.2.0-23-generic/misc/vmnet.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Networking Driver.
    author: VMware, Inc.
    srcversion: DB41C2B4C15AC67851C744F
    vermagic: 3.2.0-23-generic SMP mod_unload modversions 686
    ERROR: modinfo: could not find module vmblock
    ERROR: modinfo: could not find module vmci
    ERROR: modinfo: could not find module vsock
    filename: /lib/modules/3.2.0-23-generic/misc/vmmon.ko
    supported: external

    Starting VMware services:
    VMware USB Arbitrator done
    Virtual machine monitor done
    Virtual machine communication interface done
    VM communication interface socket family done
    Blocking file system failed
    Virtual ethernet done

    HELP please

  54. Hi,

    Running vmware workstation 7.1.6 on 3.6.6-1.fc17.x86_64 using these patches (which I had installed on previous version 3.4.blah and which were working fine) the modules compile but I get a kernel general protection fault when I start workstation:

    [ 38.874709] Modules linked in: fuse vmnet(O) ppdev parport_pc parport vmblock(O) vsock(O) vmci(O) vmmon(O) lockd sunrpc rfcomm bnep btusb nf_conntrack_ipv4 nf_defrag_ipv4 bluetooth ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables iTCO_wdt iTCO_vendor_support arc4 snd_hda_codec_idt brcmsmac cordic brcmutil mac80211 cfg80211 rfkill dell_wmi sparse_keymap dell_laptop dcdbas coretemp kvm_intel kvm microcode i2c_i801 lpc_ich mfd_core snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm bcma snd_page_alloc snd_timer snd soundcore e1000e mei uinput firewire_ohci sdhci_pci sdhci firewire_core crc_itu_t mmc_core yenta_socket ata_generic pata_acpi nouveau mxm_wmi wmi video i2c_algo_bit drm_kms_helper ttm drm i2c_core
    [ 38.875004] CPU 1
    [ 38.875004] Pid: 1818, comm: vmware-vmx Tainted: G O 3.6.6-1.fc17.x86_64 #1 Dell Inc. Precision M4400 /0G328M
    [ 38.875004] RIP: 0010:[] [] HostIF_SafeRDMSR+0xf/0×30 [vmmon]
    [ 38.875004] RSP: 0018:ffff8800d4fb5c48 EFLAGS: 00010246
    [ 38.875004] RAX: 0000000000000000 RBX: 0000000000000001 RCX: 000000000000048c
    [ 38.875004] RDX: 0000000000000000 RSI: ffff8800c3f1abd0 RDI: 000000000000048c
    [ 38.875004] RBP: ffff8800d4fb5c48 R08: ffff88011bc96a20 R09: ffffffffa0634972
    [ 38.875004] R10: 0000000000000038 R11: 0000000000003246 R12: 0000000000000000
    [ 38.875004] R13: ffff8800c3f1abc0 R14: ffff8800c3f1abc0 R15: 0000000000000042
    [ 38.875004] FS: 00007f1d22237740(0000) GS:ffff88011bc80000(0000) knlGS:0000000000000000
    [ 38.875004] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [ 38.875004] CR2: 000000000057aff0 CR3: 00000000c3eb2000 CR4: 00000000000407e0
    [ 38.875004] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    [ 38.875004] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    [ 38.875004] Process vmware-vmx (pid: 1818, threadinfo ffff8800d4fb4000, task ffff8800cb701710)
    [ 38.875004] Stack:
    [ 38.875004] ffff8800d4fb5c78 ffffffffa0636e83 ffffffffa0636e00 ffff8800d4fb5ca8
    [ 38.875004] ffff8800c3f1abc0 ffff8800c3d72700 ffff8800d4fb5c98 ffffffffa0635ed0
    [ 38.875004] ffff8800c3f1abc0 00000000013c3e90 ffff8800d4fb5cc8 ffffffffa063964c
    [ 38.875004] Call Trace:
    [ 38.875004] [] Vmx86GetMSR+0×83/0xd0 [vmmon]
    [ 38.875004] [] ? HashFunc_HashPage+0×200/0×200 [vmmon]
    [ 38.875004] [] HostIF_CallOnEachCPU+0×20/0×40 [vmmon]
    [ 38.875004] [] Vmx86_GetAllMSRs+0x2c/0×50 [vmmon]
    [ 38.875004] [] LinuxDriver_Ioctl+0×347/0x11a0 [vmmon]
    [ 38.875004] [] ? ext4_file_write+0xa9/0×490
    [ 38.875004] [] ? kmem_cache_alloc+0×31/0×160
    [ 38.875004] [] ? kmem_cache_free+0×39/0×130
    [ 38.875004] [] ? do_sync_write+0xa7/0xe0
    [ 38.875004] [] ? fsnotify+0x24b/0×340
    [ 38.875004] [] LinuxDriver_UnlockedIoctl+0×18/0×20 [vmmon]
    [ 38.875004] [] do_vfs_ioctl+0×99/0×580
    [ 38.875004] [] sys_ioctl+0×99/0xa0
    [ 38.875004] [] system_call_fastpath+0×16/0x1b
    [ 38.875004] Code: 00 00 00 00 48 89 c7 e8 f0 1d b0 e0 5d c3 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 66 66 66 66 90 31 c0 89 c2 89 f9 32 31 ff 41 89 c0 48 c1 e2 20 89 f8 4c 09 c2 48 89 16 5d c3
    [ 38.875004] RIP [] HostIF_SafeRDMSR+0xf/0×30 [vmmon]
    [ 38.875004] RSP
    [ 38.934746] —[ end trace a291bba3fbd04366 ]—

    Anyone else running on 3.6.6 x86_64? If I knew it worked in principle I could go looking for issues with my other drivers, I guess?

    Any suggestions for where else to look?

    Thanks in advance,


    • you need an asm fix additional patch for that kernel, else it’s writing over kernel data structures wrongly

      • Aha!

        Is there any source out there that shows the fix – happy to roll my own patch if necessary but I don’t know much about the actual sources so not sure where to start?



  55. OK, I fixed my problem.
    Basically, I had to get the correct patch
    I was using patch-modules_3.4.0.sh on a 3.2 kernel.
    So I got the patch-modules_3.2.0.sh file.
    I edited the patch-modules_3.2.0.sh file and changed
    as I have workstation 7.1.6.
    Then I uninstalled vmware, reinstalled it and then
    applied the patch and all worked perfectly.

    I also had to first remove a patch file, as I had already patched.

    All works now

  56. This comment is for people running 12.04 LTS on 32 bit mode and intend to install vmware player, following instruction work (please ensure that you have uninstalled any version of vmplayer first and have removed any file with name /usr/lib/vmware/modules/source/.patched )

    1) Download version 3.1.5 from vmware website –> VMware-Player-3.1.5-491717.i386.txt
    2) Download patch vmware715fixlinux320.tar.gz from http://weltall.heliohost.org/wordpress/wp-content/uploads/2012/01/
    3) Install vmware by running command (and finish installation) — sudo /bin/bash VMware-Player-3.1.5-491717.i386.txt
    4) Untar vmware715fixlinux320.tar.gz in some directory
    5) cd to that directory and run the untarred file — sudo /bin/bash patch-modules_3.2.0.sh
    6) Start the vmware player from start menu

    I have posted this since have seen web cluttered for instructions on Ubuntu 12.10 and/or vmware player 4.x . Note that on 32 bit Ubuntu any version of vmplayer greater than 3.x do not run (they will install fine but will give some error when you run them).

  57. Awesome, thanks!

  58. [...] Autor dieser Seite wird keinen Patch mehr für VMware Player 3.x anbieten, da er den Quellcode hierfür nicht mehr [...]

  59. Hi everyone;

    I Had the same problem, using Ubuntu 12.10 and VMware-player-5.0.1-894247.exe.
    After updating my system, when I run my vmplayer, I got the Error box: VMware kernel module updater.

    I can fix it with this command line:
    ~$ sudo apt-get install build-essential linux-headers-`uname -r`

    :-) it’s work now.

  60. any way to amke it work with vmplayer 3.1.1?

  61. I’ve VMware Workstation 8.0.4. Patch didn’t work for me but manually replacement of d_alloc_root(rootInode) with d_make_root(rootInode) has done the job. Thanks for instruction,

  62. [...] installed Player 3.1.6 on Ubuntu 12.04, one patch worked fine. Look for something similar to this: vmware workstation 8.0.2 7.1.5 / player 4.0.2 3.1.5 fixes for linux 3.4 | Weltall's blog (this is found on many sites and they also recommend to replace 7.1.5 with 7.1.6 in the script [...]

  63. It’s works on Fedora 17 (kernel 3.8.x), VMWare 7.1.4.
    Great thanks!

  64. Just to toss in my setup…
    Suse 12.2 with kernel 3.4.33 on vmware player 3.1.6, this patch works!

    Many thanks!!!

 Leave a Reply



You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>