May 142011
 

UPDATE5: As it seems many are using still the 7.1.x series of vmware. As vmware didn’t update the kernel sources in there but only for 8.0.0 (I wonder why… maybe marketing reasons), as some have pointed out in the comments, in order to make these patches work you just need to change the version of vmware stated in the patch script to 7.1.5 instead of 7.1.4. Same goes for the player from 3.1.4 to 3.1.5.

UPDATE4: A fix for guest kernel modules is available here

UPDATE3: It seems the patchv3 had a little bug, which prevented, at least,  building on linux 3.0.0-rc1, I’ve replaced the file so if you’ve downloaded the archive before you’ve seen this update please get it again (even more if you had issues with it)

UPDATE2: I’ve added the script which was frequently used for vmware patches in the past (had also to fix it in order to make it handle vmblock) and I’ve also updated the patch to pass the correct variable to kern_path function. vmware2.6.39patchv3.tar

This is an update to the previous post fixing some issues with the patch in the vmblock module (so it doesn’t crash anymore and it initializes properly) and should support building also on previous kernels.

Even though VMware updated their packages to support up to 2.6.38 kernel series the support for linux is still quite lacking as they forgot entirely to support 2.6.39 which was just released.

So, as it seems no one bothered yet according to google and vmware community, in order to overcome this problem I had to put my hands at sources in order to make the modules build and run under this new version of the kernel. So little by little I’ve removed many of remaining things needing the BLK or which used wrongly SPINLOCK defines (we are talking of defines which were discouraged use since some years according to kernel documentation floating around).

The process was quite successful and I could run the VM well.

Attached Files:

  • patch vmware patch for linux 2.6.39 (v2)

    Perfectly working patch for vmware in order to use it with the linux 2.6.39 kernel

  • vmware2.6.39patchv3.tar

    This patch fixes vmware products module kernels in order to run on linux 2.6.39. Changelog from the second patch: -fixed a wrong varriable being passed to kern_path -added a script based on Artem S. Tashkinov's work (it needed to be fixed in order to patch also vmblock)

  157 Responses to “Running VMware Workstation / Player on linux 2.6.39 – UPDATED”

  1. Patch error :

    /usr/lib/vmware/modules/source$ sudo patch -p0 < '/home/animehq/vmware2.6.39fixed.patch'
    [sudo] password for animehq:
    patching file source/vmblock-only/linux/dentry.c
    Hunk #1 FAILED at 103.
    1 out of 1 hunk FAILED — saving rejects to file source/vmblock-only/linux/dentry.c.rej
    patching file source/vmblock-only/linux/filesystem.c
    Hunk #1 FAILED at 44.
    Hunk #2 FAILED at 66.
    Hunk #3 FAILED at 335.
    Hunk #4 FAILED at 533.
    Hunk #5 FAILED at 552.
    Hunk #6 FAILED at 562.
    6 out of 6 hunks FAILED — saving rejects to file source/vmblock-only/linux/filesystem.c.rej
    patching file source/vmblock-only/linux/module.c
    Hunk #1 FAILED at 78.
    1 out of 1 hunk FAILED — saving rejects to file source/vmblock-only/linux/module.c.rej
    patching file source/vmci-only/linux/driver.c
    Hunk #1 FAILED at 42.
    1 out of 1 hunk FAILED — saving rejects to file source/vmci-only/linux/driver.c.rej
    patching file source/vmmon-only/linux/driver.c
    Hunk #1 FAILED at 780.
    Hunk #2 FAILED at 1041.
    2 out of 2 hunks FAILED — saving rejects to file source/vmmon-only/linux/driver.c.rej
    patching file source/vmmon-only/linux/hostif.c
    Hunk #1 FAILED at 46.
    1 out of 1 hunk FAILED — saving rejects to file source/vmmon-only/linux/hostif.c.rej
    patching file source/vmmon-only/linux/iommu.c
    Hunk #1 FAILED at 44.
    1 out of 1 hunk FAILED — saving rejects to file source/vmmon-only/linux/iommu.c.rej
    patching file source/vmnet-only/driver.c
    Hunk #1 FAILED at 28.
    Hunk #2 FAILED at 105.
    Hunk #3 FAILED at 115.
    Hunk #4 FAILED at 264.
    Hunk #5 FAILED at 1134.
    5 out of 5 hunks FAILED — saving rejects to file source/vmnet-only/driver.c.rej
    patching file source/vmnet-only/filter.c
    Hunk #1 FAILED at 85.
    1 out of 1 hunk FAILED — saving rejects to file source/vmnet-only/filter.c.rej
    patching file source/vmnet-only/hub.c
    Hunk #1 FAILED at 81.
    1 out of 1 hunk FAILED — saving rejects to file source/vmnet-only/hub.c.rej
    patching file source/vsock-only/linux/af_vsock.c
    Hunk #1 FAILED at 102.
    1 out of 1 hunk FAILED — saving rejects to file source/vsock-only/linux/af_vsock.c.rej
    patching file source/vsock-only/linux/util.c
    Hunk #1 FAILED at 34.
    1 out of 1 hunk FAILED — saving rejects to file source/vsock-only/linux/util.c.rej

    Compil error :

    mai 19 23:39:47.098: app-139846084114208| Log for VMware Workstation pid=3582 version=7.1.4 build=build-385536 option=Release
    mai 19 23:39:47.098: app-139846084114208| The process is 64-bit.
    mai 19 23:39:47.098: app-139846084114208| Host codepage=UTF-8 encoding=UTF-8
    mai 19 23:39:47.098: app-139846084114208| Logging to /tmp/vmware-root/setup-3582.log
    mai 19 23:39:47.208: app-139846084114208| modconf query interface initialized
    mai 19 23:39:47.209: app-139846084114208| modconf library initialized
    mai 19 23:39:47.231: app-139846084114208| Your GCC version: 4.5
    mai 19 23:39:47.236: app-139846084114208| Your GCC version: 4.5
    mai 19 23:39:47.245: app-139846084114208| Your GCC version: 4.5
    mai 19 23:39:47.256: app-139846084114208| Your GCC version: 4.5
    mai 19 23:39:47.265: app-139846084114208| Your GCC version: 4.5
    mai 19 23:39:47.288: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.290: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.292: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.294: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.296: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.308: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.310: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.312: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.314: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.316: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.320: app-139846084114208| Your GCC version: 4.5
    mai 19 23:39:47.328: app-139846084114208| Your GCC version: 4.5
    mai 19 23:39:47.351: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.353: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.355: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.357: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.359: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.363: app-139846084114208| Your GCC version: 4.5
    mai 19 23:39:47.371: app-139846084114208| Your GCC version: 4.5
    mai 19 23:39:47.403: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.405: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.407: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.409: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.411: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.535: app-139846084114208| Trying to find a suitable PBM set for kernel 2.6.39-2-generic.
    mai 19 23:39:47.535: app-139846084114208| Building module vmmon.
    mai 19 23:39:47.535: app-139846084114208| Extracting the sources of the vmmon module.
    mai 19 23:39:47.548: app-139846084114208| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmmon-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.39-2-generic/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.5.2
    mai 19 23:39:48.495: app-139846084114208| Failed to compile module vmmon!

    Ubuntu 11.04 kernel 2.6.39-2 vmware player 3.1.4 – 15594

    • the patch was done by extracting all packages in a folder and doing a diff between the clean packages and the edited ones extracted that way. The patches are based on 7.1.4 sources so they must be applied there and it seems it isn’t applying the patch at all in your case probably because the files are not there (as directly as files and not within packages)

      • Are there any instructions on how to implement this patch? I am relatively new to linux but have no idea where to start with the script file and the .patch file located within the zip.

        • Extract it, set execute permissions on it and run it as root or through sudo

          • As I figured, I have tried that.

            I am still receiving the same errors:

            root@brandon-X220:/usr/lib/vmware/modules/source# sh /home/brandon/Downloads/vmware2.6.39fixedv3.patch
            diff: source-orig/vmblock-only/linux/dentry.c: No such file or directory
            diff: source/vmblock-only/linux/dentry.c: No such file or directory
            /home/brandon/Downloads/vmware2.6.39fixedv3.patch: 2: —: not found
            /home/brandon/Downloads/vmware2.6.39fixedv3.patch: 3: +++: not found
            /home/brandon/Downloads/vmware2.6.39fixedv3.patch: 4: @@: not found
            /home/brandon/Downloads/vmware2.6.39fixedv3.patch: 5: Syntax error: “(” unexpected
            root@brandon-X220:/usr/lib/vmware/modules/source# sh /home/brandon/Downloads/patch-modules_2.6.39.sh
            [: 26: player3.1.4: unexpected operator
            [: 27: player3.1.4: unexpected operator
            Sorry, this script is only for VMWare WorkStation 7.1.4 or VMWare Player 3.1.4. Exiting
            root@brandon-X220:/usr/lib/vmware/modules/source# sudo patch -p0 < /home/brandon/Downloads
            patch: **** read error : Is a directory
            root@brandon-X220:/usr/lib/vmware/modules/source# sudo patch -p0 < /home/brandon/Downloads/vmware2.6.39fixedv3.patch
            patching file source/vmblock-only/linux/dentry.c
            Hunk #1 FAILED at 104.
            1 out of 1 hunk FAILED — saving rejects to file source/vmblock-only/linux/dentry.c.rej
            patching file source/vmblock-only/linux/filesystem.c
            Hunk #1 FAILED at 44.
            Hunk #2 FAILED at 66.
            Hunk #3 FAILED at 336.
            Hunk #4 FAILED at 533.
            Hunk #5 FAILED at 552.
            Hunk #6 FAILED at 563.
            6 out of 6 hunks FAILED — saving rejects to file source/vmblock-only/linux/filesystem.c.rej
            patching file source/vmci-only/linux/driver.c
            Hunk #1 FAILED at 42.
            1 out of 1 hunk FAILED — saving rejects to file source/vmci-only/linux/driver.c.rej
            patching file source/vmmon-only/linux/driver.c
            Hunk #1 FAILED at 780.
            Hunk #2 FAILED at 1041.
            2 out of 2 hunks FAILED — saving rejects to file source/vmmon-only/linux/driver.c.rej
            patching file source/vmmon-only/linux/hostif.c
            Hunk #1 FAILED at 46.
            1 out of 1 hunk FAILED — saving rejects to file source/vmmon-only/linux/hostif.c.rej
            patching file source/vmmon-only/linux/iommu.c
            Hunk #1 FAILED at 44.
            1 out of 1 hunk FAILED — saving rejects to file source/vmmon-only/linux/iommu.c.rej
            patching file source/vmnet-only/driver.c
            Hunk #1 FAILED at 28.
            Hunk #2 FAILED at 105.
            Hunk #3 FAILED at 115.
            Hunk #4 FAILED at 264.
            Hunk #5 FAILED at 1134.
            5 out of 5 hunks FAILED — saving rejects to file source/vmnet-only/driver.c.rej
            patching file source/vmnet-only/filter.c
            Hunk #1 FAILED at 85.
            1 out of 1 hunk FAILED — saving rejects to file source/vmnet-only/filter.c.rej
            patching file source/vmnet-only/hub.c
            Hunk #1 FAILED at 81.
            1 out of 1 hunk FAILED — saving rejects to file source/vmnet-only/hub.c.rej
            patching file source/vsock-only/linux/af_vsock.c
            Hunk #1 FAILED at 102.
            1 out of 1 hunk FAILED — saving rejects to file source/vsock-only/linux/af_vsock.c.rej
            patching file source/vsock-only/linux/util.c
            Hunk #1 FAILED at 34.
            1 out of 1 hunk FAILED — saving rejects to file source/vsock-only/linux/util.c.rej

          • you had to run it with bash not with sh.

          • I found a workaround that worked:

            $ mkdir /tmp/vmware && cd /tmp/vmware
            $ cp -R /usr/lib/vmware/modules/source/ .
            $ cd /tmp/vmware/source
            $ wget http://weltall.heliohost.org/wordpress/wp-content/uploads/2011/05/vmware2.6.39fixed.patch
            # if the link above does not work, an alternative is to wget http://kaslit.com/downloads/vmware2.6.39fixed.patch
            $ for i in ./*.tar; do tar -xf $i; done
            $ for i in ./*.tar; do mv $i $i.orginal; done
            $ patch –batch –force -p1 < vmware2.6.39fixed.patch
            $ tar cf vmblock.tar vmblock-only
            $ tar cf vmci.tar vmci-only
            $ tar cf vmmon.tar vmmon-only
            $ tar cf vmnet.tar vmnet-only
            $ tar cf vsock.tar vsock-only
            $ cp -vf *.tar /usr/lib/vmware/modules/source/

          • Thanks for the work around Brandon. I had to modify it to work on my machine.

            My Machine:

            Ubuntu 10.10
            Linux notebook 2.6.39-020639-generic #201105190911 SMP Thu May 19 09:14:05 UTC 2011 x86_64 GNU/Linux

            ^ Using that Kernel due to limitations with HDMI and Intel drivers on my Notebook but that’s another story… lol

            Anyways this is what I ran:


            $ mkdir /tmp/vmware && cd /tmp/vmware
            $ cp -R /usr/lib/vmware/modules/source/ .
            $ cd /tmp/vmware/source

            Copied vmware2.6.39fixedv3.patch to the source directory via drag and drop.

            $ for i in ./*.tar; do tar -xf $i; done
            $ for i in ./*.tar; do mv $i $i.orginal; done

            $ patch -t -f -p1 < vmware2.6.39fixedv3.patch

            $ tar cf vmblock.tar vmblock-only
            $ tar cf vmci.tar vmci-only
            $ tar cf vmmon.tar vmmon-only
            $ tar cf vmnet.tar vmnet-only
            $ tar cf vsock.tar vsock-only

            Got a permissions issue for "$ cp -vf *.tar /usr/lib/vmware/modules/source/" so I used sudo in front of it:

            $ sudo cp -vf *.tar /usr/lib/vmware/modules/source/

            Launched VMWare Workstation 7.1.4, it compiled everything fine and runs great.

            Thanks Brandon, and obvious thanks to Weltall!

          • worked perfectly on Ubuntu 11.10 i386 kernel 3.0.0-12 with vmware player 3.1.5

  2. Nice work. Built a gentoo-ebuild w/ your patch, works OK so far.
    I assume I am allowed to publish that ebuild?

  3. Sorry i don’t see i need to make a folder named source-original.
    thank’s for the pâtch

    • you need to extract the packages in a folder then apply it to that and repackage them after.

  4. Thank you. The patch works fine, and VMware now runs with no problems on the newly-released 2.6.39 (kernel.org), and my SatMap USB connection is now working.

    Thanks for all your work on this…

    Robert Gadsdon

  5. thanks a Lot , that works flawless on mine Ubuntu Lucid i386.
    Guys, just read all the posts to work out with 2.6.39

    Regards :)
    Harmandeep

  6. Linux Distribution: opensuse 11.4 ; kernel 2.6.39 from tumbleweed-repository

    Applied your patch without any problems. I tried to use vmware-modconfig –install-all –console to rebuild the kernel-modules. Command aborts with “unable to install vmmon”

    Used strace since there are no known (at least for me) “verbose” or “debug” switches to vmware-modconfig:

    access(“/usr/lib/vmware/modules/source/vmmon.tar”, F_OK) = -1 ENOENT (No such file or directory)

    vmmon.tar does not exist, but vmmon-only.tar is there. After establishing the links for all the tar files in the /usr/lib/vmware/modules/source directory, the above mentioned command worked without a flaw.

    • yes even though all tars contains a name-only folder the tar name itself is lacking the -only part

  7. nice work, but the patch seems to forget something to patch.

    i tried using it on openSUSE 11.4 with latest kernel 2.6.39.

    it worked until it came to building vmblock:

    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-root/modules/vmblock-only’
    make -C /lib/modules/2.6.39-30-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-2.6.39-30-obj/x86_64/desktop’
    make -C /usr/src/linux-2.6.39-30 O=/usr/src/linux-2.6.39-30-obj/x86_64/desktop/. modules
    CC [M] /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o
    /tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:69:4: error: unknown field ‘get_sb’ specified in initializer
    /tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:69:4: warning: initialization makes integer from pointer without a cast [enabled by default]
    /tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:69:4: warning: (near initialization for ‘fsType.fs_flags’) [enabled by default]
    /tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:69:4: error: initializer element is not computable at load time
    /tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:69:4: error: (near initialization for ‘fsType.fs_flags’)
    /tmp/vmware-root/modules/vmblock-only/linux/filesystem.c: In function ‘Iget’:
    /tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:339:4: error: implicit declaration of function ‘path_lookup’ [-Werror=implicit-function-declaration]
    /tmp/vmware-root/modules/vmblock-only/linux/filesystem.c: In function ‘FsOpGetSb’:
    /tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:563:4: error: implicit declaration of function ‘get_sb_nodev’ [-Werror=implicit-function-declaration]
    cc1: some warnings being treated as errors

    make[4]: *** [/tmp/vmware-root/modules/vmblock-only/linux/filesystem.o] Error 1
    make[3]: *** [_module_/tmp/vmware-root/modules/vmblock-only] Error 2
    make[2]: *** [sub-make] Error 2
    make[1]: *** [all] Error 2
    make[1]: Leaving directory `/usr/src/linux-2.6.39-30-obj/x86_64/desktop’
    make: *** [vmblock.ko] Error 2
    make: Leaving directory `/tmp/vmware-root/modules/vmblock-only’
    Unable to install vmblock

    what can i do?

    • either the patch is failing for your files (like if they where patched before) or your distro built kernel is not defining correctly things in headers. For the first check the source is correct by hand checking the patch with your source. for the second you can force the ifdef to always take the 2.6.39 path

      • i did the changes manually.
        in filesystem.c i edited line 69, and deleted the field ‘get_sb’.
        and also commented out the correspondig function in line 563.
        in line 339 i changed the call to compat_path_lookup to the call to kern_path.
        and the same in dentry.c on line 107.

        after this, it compiled.
        but when starting the vmware service with /etc/init.d/vmware start i got:

        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
        Message from syslogd@lap051-linux at May 23 12:07:09 …
        kernel:[ 1341.968771] Oops: 0010 [#2] PREEMPT SMP

        Message from syslogd@lap051-linux at May 23 12:07:09 …
        kernel:[ 1341.968776] last sysfs file: /sys/devices/virtual/misc/vsock/uevent

        Message from syslogd@lap051-linux at May 23 12:07:09 …
        kernel:[ 1341.968964] Stack:

        Message from syslogd@lap051-linux at May 23 12:07:09 …
        kernel:[ 1341.968989] Call Trace:

        Message from syslogd@lap051-linux at May 23 12:07:09 …
        kernel:[ 1341.968993] Inexact backtrace:

        Message from syslogd@lap051-linux at May 23 12:07:09 …
        kernel:[ 1341.968994]

        Message from syslogd@lap051-linux at May 23 12:07:09 …
        kernel:[ 1341.969007] Code: Bad RIP value.
        failed

        Message from syslogd@lap051-linux at May 23 12:07:09 …
        kernel:[ 1341.969007] CR2: 0000000000000000
        Virtual ethernet done

        so something i still wrong with module vmblock.

        • no you must not remove it entirely it was changed, not removed.
          Check you are using the patch attached to this post (and not the one in the previous one) the previous one was incomplete.

          You should replace .get_sb = … with .mount = …

          • only replace line
            .get_sb = FsOpGetSb,
            with
            .mount = FsOpGetSb,
            ???

            and the corresponding function in 563?

          • it seems like every line in your patch which has the check about KERNEL_VERSION bigger then 2.6.38 fails on my system.

            this check doesn’t work correctly.

          • no idea why. The same type of check (with different versions) is done by vmware developers. The only difference I see is that they use the < in place of >. That could be changed by inverting the code and placing 2.6.39 but I doubt it would gain much.
            The check works well on the vanilla kernels so I don’t know what could have been done by the package managers.
            Maybe try searching for the definition and see if the not vanilla kernel has still 2.6.38 there.
            This is how it’s defined for me (it’s in version.h and it’s generated during build)
            #define LINUX_VERSION_CODE 132647
            #define KERNEL_VERSION(a,b,c) (((a) < < 16) + ((b) << 8) + (c))

          • GREAT!
            now it works, and compiles and starts without errors.
            i did all the work, where the check for kernel bigger than 2.6.38 failed, manually by reading you patch file.
            and then it worked.
            thank you very much!

            but why does the kernel version check fail?

          • Good.
            Difficult to say from here maybe if you could post the content of include/linux/version.h. You could also try reducing the last operand to 38.

          • I’ve done a version with the check inverted but I doubt there would be changes http://weltall.heliohost.org/wordpress/wp-content/uploads/2011/05/invertedpatch.diff

          • i found /usr/src/linux-2.6.39-30-obj/x86_64/desktop/include/linux/version.h
            and the contents is:
            #define LINUX_VERSION_CODE 132647
            #define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))
            and in /usr/src/linux-obj/x86_64/desktop/include/generated/ there are:
            asm-offsets.h
            autoconf.h
            bounds.h
            utsrelease.h

            and the contents of utsrelease.h is:
            #define UTS_RELEASE "2.6.39-30-desktop"

          • and that’s correct… I’ve no idea then …

          • I’ve just tried to get a vmware appliance with opensuse 11.4 updated to tumbleweed (after a lot of dependency resolution issues) and installed gcc and vmware. Then I’ve installed the kernel desktop devel package (with correct version .39), copied the sources I’ve made the patch from and started vmware everything built at first try.
            So I can’t really see what’s the problem

          • really strange,
            thank you for your effort.
            i also can’t understand it.
            i am also on openSUSE11.4 with kernel 2.6.39-desktop from tumbleweed.
            i will try again the patch, when the next vmware release will come out.
            until then it works for me, since i have done the non-working patches manually, and they work as good as if they had benn done automatically.;-)

  8. [...] where Frank in post 7 seems to have the referenced patch working but the solution is over my head vmware workstation 7.1.4 fixes to use linux 2.6.39 (updated) | Weltall's blog Perhaps someone can understand the solution and interpret for me? Reply With Quote [...]

  9. What directory should this script be run from?

    It seems to be looking for a directory source-original that I don’t find in my workstation install.

    Thanks

    • it’s not a script it’s a patch. you need to extract the tars apply it to them and them tar them back with their original names

      • Workstation still fails to launch with the following error in log

        May 26 11:21:15.746: app-139718219626240| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmmon-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.39-30-desktop/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.5
        May 26 11:21:17.792: app-139718219626240| Failed to compile module vmmon!

        The only thing that didn’t go as I expected was the call to the download script. After several minutes of disk activity I was not returned a command prompt. I waited 5 minutes after disk activity finished and returned to command prompt using crtl C.

        • which “download script”? try to run by hand that make line and see why it fails. check also the files compare to what they should be in the tars

  10. My distro is same as Frank in post 7 above.

    openSuse 11.4 Tumbleweed

  11. Hi, just applied your patch without problems the source files and repacked them afterwards, but not to VMware player but to VMware workstation! System was openSUSE 11.4 Tumbleweed. When trying to install the modules I get the following error message:


    Stopping VMware services:
    VMware USB Arbitrator done
    VM communication interface socket family done
    Virtual machine communication interface done
    Virtual machine monitor done
    Blocking file system done
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-root/modules/vmmon-only'
    make -C /lib/modules/2.6.39-30-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-2.6.39-30-obj/i386/desktop'
    make -C ../../../linux-2.6.39-30 O=/usr/src/linux-2.6.39-30-obj/i386/desktop/. modules
    CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o
    /tmp/vmware-root/modules/vmmon-only/linux/driver.c:784:59: error: ‘SPIN_LOCK_UNLOCKED’ undeclared here (not in a function)
    make[4]: *** [/tmp/vmware-root/modules/vmmon-only/linux/driver.o] Fehler 1
    make[3]: *** [_module_/tmp/vmware-root/modules/vmmon-only] Fehler 2
    make[2]: *** [sub-make] Fehler 2
    make[1]: *** [all] Fehler 2
    make[1]: Leaving directory `/usr/src/linux-2.6.39-30-obj/i386/desktop'
    make: *** [vmmon.ko] Fehler 2
    make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'

    At the position where the error raised in driver.c I have the following code:

    #define POLLQUEUE_MAX_TASK 1000
    static spinlock_t pollQueueLock __attribute__((unused)) = SPIN_LOCK_UNLOCKED;
    static void *pollQueue[POLLQUEUE_MAX_TASK];
    static unsigned int pollQueueCount = 0;

    Any ideas what is going wrong here?

    Andi

    • No that macro is supposed to be there since years in the kernel, plus I’ve tried opensuse and it worked well.

    • ok it seems your problem is like for others that the patch didn’t apply. If it applied correctly you would have DEFINE_SPINLOCK.
      If you are trying to patch previously patched files or files from 7.1.3 that’s likely to fail. You need 7.1.4 clean sources in order to apply this patch (else manual patching will always work for previous versions)

  12. tnx 4 help

  13. Works perfect! Thanks!!!

  14. Patch V3 works perfectly on debian unstable. Thank you very much !

  15. Thank you! It works great.

  16. Hi Guys,

    I can confirm that this patch also works with linux kernel 3.0.0-rc1:

    cp -f vsock.ko ./../vsock.o
    make: Leaving directory `/tmp/vmware-root/modules/vsock-only’
    No protocol specified
    No protocol specified
    No protocol specified
    No protocol specified
    Built vsock module
    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 done
    Virtual ethernet done
    Shared Memory Available done

    All done, you can now run VMWare WorkStation.
    Modules sources backup can be found in the ‘/usr/lib/vmware/modules/source-workstation7.1.4-2011-05-31-21:16:12-backup’ directory
    root@glaptop:/home/ggorosito/Downloads/vmware/3.0.0/v3# uname -a
    Linux glaptop 3.0.0-rc1 #1 SMP Tue May 31 18:53:25 ART 2011 x86_64 GNU/Linux

    Also, I’ve got this working on debian wheezy

  17. Hi,

    Work very well on Debian sid and kernel unstable 2.6.39

    Great work, enjoy !

  18. great: patchv3 version works with 3.1 vmware-player
    thx!

  19. Thank very much , Work very well on Archlinux kernel26-ck 2.6.39 kernel

  20. Excellent patch! Works well on Gnome 3 Debian wheezy 2.6.39-2 :)

  21. Thank you very very much! You are saved my life :)

  22. At first I had problems with compiling vmnet and vmci modules. The original two tar archives had tmp/vmnet-only and tmp/vmci-only path. So I repackaged those two modules the same way after patching. And failed while trying to use Vmware Workstation …
    After repackaging those two modules without that “tmp” part, Workstation managed to compile and load those two modules as well.

    I don’t have the slightest idea what created that “tmp” in those two tar files, but – it works now, thanks for the patch!

  23. Your v3 fix works well on Archlinux as well. Thanks for your great job!!!

  24. Confirmed to work on lucid with a 2.6.39.1 kernel.

    I had to reboot in order to get rid of the old (buggy) vmblock kernel module. It seems to be a ‘load once and never unload’ module.

  25. This is geared entirely to linux Hosts.

    What if we are virtualizing linux as the Guest OS, which is what most people will be doing with a non long-term-supported kernel in the first place?

  26. Thank you for your efforts, the patch works fine on my machine, but when I try to build It get this error

    sudo /usr/bin/make -C /tmp/vmware-root/modules/vmmon-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.39-0-generic/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.5.2
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-root/modules/vmmon-only’
    make -C /lib/modules/2.6.39-0-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-headers-2.6.39-0-generic’
    CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o
    /tmp/vmware-root/modules/vmmon-only/linux/driver.c:783:59: error: ‘SPIN_LOCK_UNLOCKED’ undeclared here (not in a function)
    make[2]: *** [/tmp/vmware-root/modules/vmmon-only/linux/driver.o] Error 1
    make[1]: *** [_module_/tmp/vmware-root/modules/vmmon-only] Error 2
    make[1]: Leaving directory `/usr/src/linux-headers-2.6.39-0-generic’
    make: *** [vmmon.ko] Error 2
    make: Leaving directory `/tmp/vmware-root/modules/vmmon-only’

    I’m on ubuntu natty 64 with kernel 2.6.39-0-generic.
    I could not find what SPIN_LOCK_UNLOCKED is, any idea?

    • It’s define spinlock. But the problem in your case is that the patch didn’t apply

      • You absolutely right, I was patching the files but copying the original tars back :) your patch works great. Many thanks.
        M

  27. Thank you that did the trick perfectly!

  28. It worked smoothly with 3.0.0-rc7. Thanks for your effort!

  29. Hi @all,

    i’ve applied your patch V3, but my vmware-player 3.1.4 gives me a signal 11! I’am using debian testing with 2.6.39-2-686-pae kernel.

    Is there any possibility to upload a log file?


    Jul 18 13:15:52.239: vcpu-0| SymBacktrace[0] 0xad0b6938 eip 0x8058fd0 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0x8048000
    Jul 18 13:15:52.239: vcpu-0| SymBacktrace[1] 0xad0b6d68 eip 0x8132960 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0x8048000
    Jul 18 13:15:52.239: vcpu-0| SymBacktrace[2] 0xad0b6e28 eip 0x80c96cf in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0x8048000
    Jul 18 13:15:52.239: vcpu-0| SymBacktrace[3] 0xad0b7208 eip 0xb77da40c in function __kernel_rt_sigreturn in object loaded at 0xb77da000
    Jul 18 13:15:52.239: vcpu-0| SymBacktrace[4] 0xad0b7238 eip 0x850233b in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0x8048000
    Jul 18 13:15:52.239: vcpu-0| SymBacktrace[5] 0xad0b7278 eip 0x84d7dce in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0x8048000
    Jul 18 13:15:52.239: vcpu-0| SymBacktrace[6] 0xad0b7288 eip 0x85022b1 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0x8048000
    Jul 18 13:15:52.239: vcpu-0| SymBacktrace[7] 0xad0b7378 eip 0x80ca258 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0x8048000
    Jul 18 13:15:52.239: vcpu-0| SymBacktrace[8] 0xad0b7478 eip 0xb7785c39 in function (null) in object /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 loaded at 0xb7780000
    Jul 18 13:15:52.239: vcpu-0| SymBacktrace[9] 00000000 eip 0xb758693e in function clone in object /lib/i386-linux-gnu/i686/cmov/libc.so.6 loaded at 0xb74ba000
    Jul 18 13:15:52.239: vcpu-0| Msg_Post: Error
    Jul 18 13:15:52.239: vcpu-0| [msg.log.error.unrecoverable] VMware Player unrecoverable error: (vcpu-0)
    Jul 18 13:15:52.239: vcpu-0| Unexpected signal: 11.
    Jul 18 13:15:52.239: vcpu-0| [msg.panic.haveLog] A log file is available in "/usr/people/VMWARE_Machines/Windows_7_64Bit/vmware.log". [msg.panic.requestSupport.withLog] Please request support and include the contents of the log file. [msg.panic.requestSupport.vmSupport.windowsOrLinux.player]
    Jul 18 13:15:52.239: vcpu-0| To collect data to submit to VMware support, run "vm-support".
    Jul 18 13:15:52.239: vcpu-0| [msg.panic.response] We will respond on the basis of your support entitlement.
    Jul 18 13:15:52.239: vcpu-0| ----------------------------------------

    • could use pastebin. But that doesn’t really look like an issue with the modules (you would see that in dmesg) rather an issue with the specific vm (vm settings/guest os) or with the userland install.

  30. Perfect!!!! thanks!

  31. Patch V3 worked great running on Debian Testing with 3.0.0-1-amd64.

    Thanks!

  32. [...] Downloaded vmware2.6.39patchv3.tar – [...]

  33. I’m sure this is a different issue, but I’ve searched high and low and found nothing on it. I’m using 3.0.0-git13 on gentoo. Have your patch applied in an overlay. Patch completes fine. My issue is with building vmnet. Get a bunch of issues for conflicting types within vmnet-only/compat_netdevice.h

    I’m guessing I have something enabled in the kernel that should not be? I did make sure KVM was disabled.

    • There is a bigger probability the kernel API got broken as that kernel is actually the merge window version of 3.1. I will probably have a look at it when 3.1 rc1 gets released so it’s bot going to change anymore

  34. Worked well for me too, after making a small adjustment to the shell script.

    The vmware-installer -l command on my PC is returning

    Product Name Product Version
    ====================== ====================
    vmware-vix 1.9.0.261024
    vmware-player 3.1.4.385536

    and that was confusing the version check so I just grepped out the player line and it all ran fine.

    Matt

  35. It seems that the vmware patch does not work.


    HOSTNAME:~# LANG=C
    HOSTNAME:~# cd /tmp

    Download the file VMware-Player-3.1.4-385536.x86_64.bundle

    HOSTNAME:/tmp# chmod +x VMware-Player-3.1.4-385536.x86_64.bundle
    HOSTNAME:/tmp# mkdir /tmp/vmware
    HOSTNAME:/tmp# ./VMware-Player-3.1.4-385536.x86_64.bundle -x /tmp/vmware/3.1.4
    Extracting VMware Installer...done.
    Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyHOSTNAME:/tmp#
    HOSTNAME:/tmp# cp -a /tmp/vmware/3.1.4/vmware-player-app/lib/modules/source/ /tmp/vmware/
    HOSTNAME:/tmp# cd /tmp/vmware/source/
    HOSTNAME:/tmp/vmware/source# find -type f -exec tar xf '{}' \;
    HOSTNAME:/tmp/vmware/source# wget -O - http://weltall.heliohost.org/wordpress/wp-content/uploads/2011/05/vmware2.6.39patchv3.tar.bz2 |tar xj vmware2.6.39fixedv3.patch
    --2011-08-06 13:52:27-- http://weltall.heliohost.org/wordpress/wp-content/uploads/2011/05/vmware2.6.39patchv3.tar.bz2
    Resolving weltall.heliohost.org (weltall.heliohost.org)... 216.218.192.170
    Connecting to weltall.heliohost.org (weltall.heliohost.org)|216.218.192.170|:80...
    connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 3740 (3.7K) [application/x-bzip2]
    Saving to: `STDOUT'

    100%[=====================================================================================================================================================================================================================================>] 3,740 18.2K/s in 0.2s

    2011-08-06 13:52:28 (18.2 KB/s) - written to stdout [3740/3740]

    HOSTNAME:/tmp/vmware/source# patch -p1 < vmware2.6.39fixedv3.patch
    patching file vmblock-only/linux/dentry.c
    patching file vmblock-only/linux/filesystem.c
    patching file vmci-only/linux/driver.c
    patching file vmmon-only/linux/driver.c
    patching file vmmon-only/linux/hostif.c
    patching file vmmon-only/linux/iommu.c
    patching file vmnet-only/driver.c
    patching file vmnet-only/filter.c
    patching file vmnet-only/hub.c
    patching file vsock-only/linux/af_vsock.c
    patching file vsock-only/linux/util.c
    HOSTNAME:/tmp/vmware/source# for i in vmblock vmci vmmon vmnet vsock; do tar cf ${i}.tar ${i}-only; done
    HOSTNAME:/tmp/vmware/source# mv -f *.tar /usr/lib/vmware/modules/source/
    HOSTNAME:/tmp/vmware/source# vmware-modconfig --console --install-all
    Stopping VMware services:
    VMware USB Arbitrator done
    VM communication interface socket family done
    Virtual machine communication interface done
    Virtual machine monitor done
    Blocking file system done
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-root/modules/vmmon-only'
    make -C /lib/modules/3.0.0-1-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-headers-3.0.0-1-amd64'
    Makefile:10: *** mixed implicit and normal rules. Stop.
    make[1]: Leaving directory `/usr/src/linux-headers-3.0.0-1-amd64'
    make: *** [vmmon.ko] Error 2
    make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
    Unable to install vmmon
    HOSTNAME:/tmp/vmware/source#

    Any ideas what is going wrong here?

  36. HOSTNAME:/tmp/vmware/source# uname -a
    Linux kay-desktop 3.0.0-1-amd64 #1 SMP Sun Jul 24 02:24:44 UTC 2011 x86_64 GNU/Linux
    kay-desktop:/tmp/vmware/source# lsb_release -a
    LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:qt4-3.1-amd64:qt4-3.1-noarch
    Distributor ID: Debian
    Description: Debian GNU/Linux unstable (sid)
    Release: unstable
    Codename: sid
    HOSTNAME:/tmp/vmware/source# uname -a
    Linux kay-desktop 3.0.0-1-amd64 #1 SMP Sun Jul 24 02:24:44 UTC 2011 x86_64 GNU/Linux

  37. Man, you’re a lifesaver – I would had to install another kernel if it wasn’t for you… worked flawlessly with kernel 2.6.40 (fedora 15) and wmplayer 3.1.4

    Thanks!

  38. Latest 2.6.39 patch works fine with kernel.org 3.0 and 3.0.1, but vmnet compile fails with 3.1-rc1:


    make: Entering directory `/tmp/vmware-root/modules/vmnet-only'
    make -C /lib/modules/3.1.0-rc1/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-3.1-rc1'
    CC [M] /tmp/vmware-root/modules/vmnet-only/netif.o
    In file included from /tmp/vmware-root/modules/vmnet-only/netif.c:43:0:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:186:0: warning: "alloc_netdev" redefined [enabled by default]
    include/linux/netdevice.h:2438:0: note: this is the location of the previous definition
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:187:0: warning: "alloc_etherdev" redefined [enabled by default]
    include/linux/etherdevice.h:53:0: note: this is the location of the previous definition
    In file included from /tmp/vmware-root/modules/vmnet-only/netif.c:43:0:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: error: conflicting types for ‘netif_start_queue’
    include/linux/netdevice.h:1804:51: note: previous definition of ‘netif_start_queue’ was here
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In function ‘netif_start_queue’:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:210:21: error: ‘struct device’ has no member named ‘tbusy’
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: At top level:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: error: conflicting types for ‘netif_stop_queue’
    include/linux/netdevice.h:1869:51: note: previous definition of ‘netif_stop_queue’ was here
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In function ‘netif_stop_queue’:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:216:19: error: ‘struct device’ has no member named ‘tbusy’
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: At top level:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:220:1: error: conflicting types for ‘netif_queue_stopped’
    include/linux/netdevice.h:1895:50: note: previous definition of ‘netif_queue_stopped’ was here
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In function ‘netif_queue_stopped’:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:68: error: ‘struct device’ has no member named ‘tbusy’
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:108: error: ‘struct device’ has no member named ‘tbusy’
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: At top level:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:226:1: error: conflicting types for ‘netif_wake_queue’
    include/linux/netdevice.h:1838:51: note: previous definition of ‘netif_wake_queue’ was here
    .....................

  39. Thanks for the patch.

  40. worked flawlessly with debian testing 3.0.0-1-amd64

  41. you are my HERO!!!!

    Thank you soooo much for this patch!!! i had nearly given up the idea of running vmware on my ubuntu 11.04 with a 2.6.39 kernel!

    Thank you for sharing this!

  42. THANK YOU

  43. AWESOME! Thank you very much! It took me a few times to get it right but this did work for me.

    Running BT5R1 (Kernel 2.6.39.4) VMWare Workstation 7.1.4

    I cannot thank you guys enough!!

    Scott says:
    July 21, 2011 at 23:17

    Thanks for the work around Brandon. I had to modify it to work on my machine.

    My Machine:

    Ubuntu 10.10
    Linux notebook 2.6.39-020639-generic #201105190911 SMP Thu May 19 09:14:05 UTC 2011 x86_64 GNU/Linux

    ^ Using that Kernel due to limitations with HDMI and Intel drivers on my Notebook but that’s another story… lol

    Anyways this is what I ran:

    $ mkdir /tmp/vmware && cd /tmp/vmware
    $ cp -R /usr/lib/vmware/modules/source/ .
    $ cd /tmp/vmware/source

    Copied vmware2.6.39fixedv3.patch to the source directory via drag and drop.

    $ for i in ./*.tar; do tar -xf $i; done
    $ for i in ./*.tar; do mv $i $i.orginal; done

    $ patch -t -f -p1 < vmware2.6.39fixedv3.patch

    $ tar cf vmblock.tar vmblock-only
    $ tar cf vmci.tar vmci-only
    $ tar cf vmmon.tar vmmon-only
    $ tar cf vmnet.tar vmnet-only
    $ tar cf vsock.tar vsock-only

    Got a permissions issue for "$ cp -vf *.tar /usr/lib/vmware/modules/source/" so I used sudo in front of it:

    $ sudo cp -vf *.tar /usr/lib/vmware/modules/source/

    Launched VMWare Workstation 7.1.4, it compiled everything fine and runs great.

    Thanks Brandon, and obvious thanks to Weltall!

  44. I confirm patch work on kernel 3.0.3 form kernel.org (own compile) with VMware-Player-3.1.4-385536.x86_64 on AMD 64 processor on Mandriva 2010.2 x86_64.

  45. Thanks Souless, your procedure is great!
    Worked on kernel 3.0.0-10-generic on Ubuntu 11.10 Oneiric Ocelot.

  46. Thanks Souless, your procedure is great!

    Worked on kernel 3.0.0-10-generic on Ubuntu 11.10 Oneiric Ocelot.

  47. Fedora 15 (Linux 2.6.40.3-0.fc15.x86_64)
    VMware Workstation 7.1.4 build-385536

    WORKING

    Weltall = #1

  48. Hi.

    I’m working on a SLES11 system with the 3.0.3 Kernel from the stable-directory-
    ( http://download.opensuse.org/repositories/Kernel:/stable/standard/x86_64/ )
    Patched the the modules of vmware 7.1.4.
    Compiling was no problem.
    Problem is loading the vmblock module.
    It gives me a kernel panic everytime.
    So I removed the loading of the vmblock module out of the vmware start script.
    Stopping the vmware is also a problem.
    Unloading the modules creates a kernel panic.

    Could you please help me?
    What do you need for support?

    • You are using an old version of the patch. Download the newest one and patch the clean files.

      • Hi Weltall.

        I’m sorry to dissapoint you. I’m using the v3 of the patch and clean sources of the 7.1.4 vmware. No luck at all.

        • Hi again.
          I am sorry. I had to be more precise. I used the “kernel-default”.
          Today i tested the “kernel-vanilla” and everything is ok.
          As a conclusion i think that one or more of the SuSE patches break something.

          For now I can live with the vanilla flavor, but I will start a case at SuSE.

          Thanks for the patch!

  49. [...] but is sure if I apply it? I'll need recompile the kernel without an official opensuse patch. http://…/running-vmware-workstation-player-on-linux-2-6-39-updated Bye Reply With Quote + Reply to Thread « Previous Thread | Next [...]

  50. Thank you so much!!!! I owe you a lot… this really worked for me!!! i’ve searched google for 4 hours… and here you are.. hehe.. thanks a lot!!!

  51. Thank you thank you thank you!!!

    I REALLY needed to get vmware working tonight, and I was just about to split my main linux partition and install a downgraded version of my distro when i found this. Worked like a charm and saved the day!

  52. Hi,
    I’ve used “vmware2.6.39patchv3.tar” in ubuntu 11.10 (3.0.0-9-generic) with VMPlayer 3.1.4.
    It works perfectly.

    Thanks

    • Hi,
      I use ubuntu 11.10 , too. But vmware 7.1.4 not run,
      Can you help me????
      this is log file after I install it :
      Nov 08 08:47:44.027: app-3079198400| Log for VMware Workstation pid=5780 version=7.1.4 build=build-385536 option=Release
      Nov 08 08:47:44.027: app-3079198400| The process is 32-bit.
      Nov 08 08:47:44.027: app-3079198400| Host codepage=UTF-8 encoding=UTF-8
      Nov 08 08:47:44.027: app-3079198400| Logging to /tmp/vmware-root/setup-5780.log
      Nov 08 08:47:44.172: app-3079198400| modconf query interface initialized
      Nov 08 08:47:44.173: app-3079198400| modconf library initialized
      Nov 08 08:47:44.205: app-3079198400| Your GCC version: 4.6
      Nov 08 08:47:44.213: app-3079198400| Your GCC version: 4.6
      Nov 08 08:47:44.226: app-3079198400| Your GCC version: 4.6
      Nov 08 08:47:44.245: app-3079198400| Your GCC version: 4.6
      Nov 08 08:47:44.263: app-3079198400| Your GCC version: 4.6
      Nov 08 08:47:44.309: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.314: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.318: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.322: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.326: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.353: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.357: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.362: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.366: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.370: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.378: app-3079198400| Your GCC version: 4.6
      Nov 08 08:47:44.401: app-3079198400| Your GCC version: 4.6
      Nov 08 08:47:44.543: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.551: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.559: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.564: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.570: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.579: app-3079198400| Your GCC version: 4.6
      Nov 08 08:47:44.595: app-3079198400| Your GCC version: 4.6
      Nov 08 08:47:44.692: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.698: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.703: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.708: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:44.714: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:45.233: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:47:45.234: app-3079198400| Building module vmmon.
      Nov 08 08:47:45.234: app-3079198400| Extracting the sources of the vmmon module.
      Nov 08 08:47:45.277: app-3079198400| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmmon-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/3.0.0-12-generic/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.6.1
      Nov 08 08:47:49.423: app-3079198400| Failed to compile module vmmon!
      Nov 08 08:57:26.043: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:57:26.050: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:57:26.057: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:57:26.063: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:57:26.070: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:57:26.079: app-3079198400| Your GCC version: 4.6
      Nov 08 08:57:26.100: app-3079198400| Your GCC version: 4.6
      Nov 08 08:57:26.189: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:57:26.196: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:57:26.202: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:57:26.208: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:57:26.215: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.
      Nov 08 08:57:26.538: app-3079198400| Trying to find a suitable PBM set for kernel 3.0.0-12-generic.

  53. hi all
    i test it work 100%
    tanks alot

  54. Patches for VMware® Workstation 7.1.4 build-385536
    for Linux kernel 3.0.3 and 3.0.3-rt12 (RealTime patch)

    http://pavlinux.ru/vmware/7.1.4/

  55. Thanks to all, specially to Weltall
    these are the needed steps on Ubuntu Linux 3*

    $ lsb_release -rd
    Description: Ubuntu oneiric (development branch)
    Release: 11.10

    $ uname -a
    Linux myUBT 3.0.0-9-generic #15-Ubuntu SMP Tue Aug 30 15:03:37 UTC 2011 i686 i686 i386 GNU/Linux

    ——-
    STEPS:
    ——-
    Close VMware dialog from where you got the error. (no need to uninstall/remove VMware)

    sudo -i
    mkdir /tmp/vmware && cd /tmp/vmware
    cp -R /usr/lib/vmware/modules/source/
    cp -R /usr/lib/vmware/modules/source/ /tmp/vmware
    cd /tmp/vmware/source
    wget http://weltall.heliohost.org/wordpress/wp-content/uploads/2011/05/vmware2.6.39patchv3.tar.bz2
    tar -jxvf vmware2.6.39patchv3.tar.bz2
    for i in ./*.tar; do tar -xf $i; done
    for i in ./*.tar; do mv $i $i.orginal; done
    patch -t -f -p1 < vmware2.6.39fixedv3.patch
    tar cf vmblock.tar vmblock-only
    tar cf vmci.tar vmci-only
    tar cf vmmon.tar vmmon-only
    tar cf vmnet.tar vmnet-only
    tar cf vsock.tar vsock-only
    cp -vf *.tar /usr/lib/vmware/modules/source/

    Run VMware

  56. Working – Ubuntu Oneric Beta 1, kernel 3.0.0-10-generic x86_64, VMWare Workstation 7.1.4 build-385536


    su
    cd /usr/src/
    mkdir vmware.patch
    cd vmware.patch
    wget http://weltall.heliohost.org/wordpress/wp-content/uploads/2011/05/vmware2.6.39patchv3.tar.bz2
    tar xfvj vmware2.6.39patchv3.tar.bz2
    bash patch-modules_2.6.39.sh

  57. Perfect work!
    Worked on my ArchLinux box.
    Thank you!

  58. Works great on my 2.6.39-rc6 running on my Asus G73SW
    Artem, you are The Man!

    Thanks!

  59. awesome! it worked like a charm on Fedora 15 ;)
    thanks!

  60. Workstation 7.1.5 breaks the patch (on Ubuntu Oneiric 3.0.12), but it can be fixed like:

    rm /usr/lib/vmware/modules/source/.patched
    vi patch-modules_2.6.39.sh
    #vmreqver=7.1.4 (copy this line, then comment it out)
    vmreqver=7.1.5 (add this line right below it)
    bash patch-modules_2.6.39.sh

    It still prompts me to re-compile the modules every time I start vmware, but I have to guess that’s a problem on VMWare’s end still?

    • I didn’t know they have released 7.1.5. As right now I’m not using 7 anymore i can’t verify it. Anyway usually the request to recompile modules could happen mostly in two cases according to my experience: the modules couldn’t be found in the modules folder or are named wrongly or the modules didn’t load for some reason. (caught oops usually show just an error during the compilation but after that it won’t show any other error or request)

  61. On Dreamlinux 3.5 upgraded to squeeze base – refused to patch on player 3.1.5

    Changed the patch line :
    plreqver=3.1.4
    to
    plreqver=3.1.5
    and all’s well :-)

  62. What a shame for VMware – new version 7.1.5 and still the same bug :-( . But thanks to Weltall I was able to get the workstation up on an openSUSE 11.4 with kernel 3.0.4-43-desktop #1 SMP PREEMPT. Just changed the required version in the script (see postings above) and everythink worked.

    Thank you!

  63. worked on fedora 15, kernel 2.6.40 and vmware workstation 7.1.5 build-491717.

    thanks, this is the second time i have used this solution.

  64. Thanks, I just used this on Ubuntu 11.10 with vmware 7.1.5

  65. Hi Weltall

    Excellent work !! I ran your shell script and Vmware Player started right up. You are on page 2 of google search, and should be on page one. Keep up the good work.

    Jim

  66. Thank you so much for this patch! It worked perfectly in Ubuntu 11.10 with WS 7.1.5 after I changed the max version at the beginning of the script.

  67. [...] 7.1.4 with Linux kernel 3.0.0-12. Then I found a user in this thread who pointed to the solution at Weltall’s Blog. Weltall created the necessary fixes along with a script to install them. Although targeted for [...]

  68. The patch worsk also for VMWare Player 3.1.5 on Ubuntu 11.10. You just need to change the plreqver value in the patch-modules_2.6.39.sh script (line 8) to say 3.1.5 instead of 3.1.4

  69. Thank you very much.
    Your patch works perfectly in my ubuntu 11.10 kernel 3.0.0-12 generic system.
    Linux 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

  70. After a bit of file manipulation, it works like a charm!

    Thanks a bunch,

    G.

  71. Wow! A lifesaver! I’m relieved, and thank you!

  72. Thanks very much!

  73. Awesome!!! thanks worked for my installation of 11.10…

  74. It has worked for Ubuntu 11.10. Thanks…

  75. This worked for my install of Ubuntu 11.10! After much searching and hairpulling. Thank you!!!

  76. Beautiful! Thank you.

    Worked for me on Ubuntu 11.10 for VM Workstation 7.1.5 and kernel 3.0.0-12 generic

  77. i am using VMware 7.1.4-385536 and Ubuntu 11.10 with kernel 3.0.0.12. I am unable to apply the patch.

    ****************
    root@ocean13-Reserved:/usr/src/vmware.patch# bash patch-modules_2.6.39.sh
    patching file vmblock-only/linux/dentry.c
    patching file vmblock-only/linux/filesystem.c
    can’t find file to patch at input line 109
    Perhaps you used the wrong -p or –strip option?
    The text leading up to this was:
    ————————–
    |diff -u -r source-orig/vmci-only/linux/driver.c source/vmci-only/linux/driver.c
    |— source-orig/vmci-only/linux/driver.c 2011-03-26 06:37:32.000000000 +0100
    |+++ source/vmci-only/linux/driver.c 2011-04-02 13:32:12.000000000 +0200
    ————————–
    File to patch: q
    q: No such file or directory
    Skip this patch? [y]
    Skipping patch.
    1 out of 1 hunk ignored
    *******************************************************

    and the errors goes on… can you please help? thanks

  78. another ocelot-victim.. another “thank you” :-)

  79. Hello, I’m running Debian 6 (Squeeze) amd64 but with 3.1.0 kernel for a new Realtek wireless driver. Vmware workstation version is 7.1.5, For some reason kmap and kunmap argument is wrong type in userif.c. the other vmware modules compile correctly with your patch, thanks for doing very helpful thing for a lot of people!

    CC [M] /tmp/vmware-root/modules/vmnet-only/userif.o
    /tmp/vmware-root/modules/vmnet-only/userif.c: In function ‘VNetCsumCopyDatagram’:
    /tmp/vmware-root/modules/vmnet-only/userif.c:575: error: incompatible type for argument 1 of ‘kmap’
    include/linux/highmem.h:48: note: expected ‘struct page *’ but argument is of type ‘const struct ’
    /tmp/vmware-root/modules/vmnet-only/userif.c:578: error: incompatible type for argument 1 of ‘kunmap’
    include/linux/highmem.h:54: note: expected ‘struct page *’ but argument is of type ‘const struct ’

  80. It failed when applied to vmplayer 4 on kernel 3.0.0.12, Ubunto 11.10.
    Somebody knows a workaround for it?

  81. I used this patch for vmware 7.1.4 on ubuntu 11.10
    Works perfectly. Thank you!

  82. Time to switch to virtualbox. Thanks for the memories…

  83. For 3.1 An additional change is necessary to vmnet-only/compat_netdevice.h

    --- compat_netdevice.h.orig 2011-03-25 22:37:29.000000000 -0700
    +++ compat_netdevice.h 2011-11-28 13:21:05.952467009 -0800
    @@ -26,6 +26,17 @@
    #include

    /*
    + * As of 3.1 Linux no longer has feature test macros.
    + */
    +#if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 1, 0)
    +#define HAVE_ALLOC_NETDEV /* alloc_netdev() */
    +#define HAVE_FREE_NETDEV /* free_netdev() */
    +#define HAVE_NETDEV_PRIV /* netdev_priv() */
    +#define HAVE_NET_DEVICE_OPS
    +#define HAVE_NETIF_QUEUE
    +#endif
    +
    +/*
    * The enet_statistics structure moved from linux/if_ether.h to
    * linux/netdevice.h and is renamed net_device_stats in 2.1.25 --hpreg
    */

  84. Applied via Comment #44 successfully, verbatim.

    Ubuntu 11.10 (Oneiric Ocelot)
    3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
    VMware Workstation 7.1.4 build-385536

    Thanks.

  85. [...] This article(see comment:56) is written for 3.0.0.9 but works fine for newer kernals also. 123$ lsb_release -rd Description: Ubuntu oneiric (development branch) Release: 11.10 [...]

  86. There’s a slight error in the v3 patch. Line 29 and 30. $vmreqver and $plreqver should be outside of quotes. The comparison is taking it literally inside the quotes, atm.

  87. Hi, I tried it yesterday with a 3.0.0-12 kernel (Ubuntu) but when I upgraded to 3.0.0-14 I had to recompile and the patch didn’t run. First it mentioned it was already patched so I deleted the .patched file, then it spit out more errors…

    patching file vmblock-only/linux/dentry.c
    Reversed (or previously applied) patch detected! Assume -R? [n] y
    patching file vmblock-only/linux/filesystem.c
    Reversed (or previously applied) patch detected! Assume -R? [n] y
    patching file vmci-only/linux/driver.c
    Reversed (or previously applied) patch detected! Assume -R? [n] y
    patching file vmmon-only/linux/driver.c
    Reversed (or previously applied) patch detected! Assume -R? [n] y
    Hunk #1 succeeded at 785 (offset 5 lines).
    Hunk #2 succeeded at 1046 (offset 5 lines).
    patching file vmmon-only/linux/hostif.c
    Reversed (or previously applied) patch detected! Assume -R? [n] y
    patching file vmmon-only/linux/iommu.c
    Reversed (or previously applied) patch detected! Assume -R? [n] y
    patching file vmnet-only/driver.c
    Reversed (or previously applied) patch detected! Assume -R? [n] y
    patching file vmnet-only/filter.c
    Reversed (or previously applied) patch detected! Assume -R? [n] y
    patching file vmnet-only/hub.c
    Reversed (or previously applied) patch detected! Assume -R? [n] y
    patching file vsock-only/linux/af_vsock.c
    Reversed (or previously applied) patch detected! Assume -R? [n] y
    patching file vsock-only/linux/util.c
    Reversed (or previously applied) patch detected! Assume -R? [n] y
    Stopping VMware services:
    VMware USB Arbitrator done
    VM communication interface socket family done
    Virtual machine communication interface done
    Virtual machine monitor done
    Blocking file system done
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-root/modules/vmmon-only’
    make -C /lib/modules/3.0.0-14-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-headers-3.0.0-14-generic’
    CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o
    /tmp/vmware-root/modules/vmmon-only/linux/driver.c:788:59: error: ‘SPIN_LOCK_UNLOCKED’ undeclared here (not in a function)
    make[2]: *** [/tmp/vmware-root/modules/vmmon-only/linux/driver.o] Error 1
    make[1]: *** [_module_/tmp/vmware-root/modules/vmmon-only] Error 2
    make[1]: Leaving directory `/usr/src/linux-headers-3.0.0-14-generic’
    make: *** [vmmon.ko] Error 2
    make: Leaving directory `/tmp/vmware-root/modules/vmmon-only’
    Unable to install vmmon

    Any ideas?

    • first of all if you assume -r you are reverting the patch so essentially unpatching.
      second in order to rebuild after an update just launch vmware and it will build the modules by itself, after patching you don’t need to use the patch and the script any more.

  88. Any chance this can be updated to kernel 3.2? I recently update my debian testing to it.

  89. Thanks to Weltall for making this patch. Appreciate the effort to help those out there who cannot help themselves, kudos to you sir.

    Thanks also to Souless for taking the time to post your steps as well.

    Here are the exact steps that I have taken for VMware Workstation 7.1.5, with Player 3.1.5, latest for version 7 from the VMware website as of March-06-2012. This was for an Ubuntu 11.10 oneiric x64 platform, 3.0.0-16 generic kernel, running VMware Workstation 7.1.5 and Player 3.1.5;

    1. Extract the contents of the vmware2.6.39patchv3.tar.bz2 file,
    then open the patch-modules_2.6.39.sh file with gedit

    2. Change these 2 lines at the top of the script file;

    from this:
    vmreqver=7.1.4
    plreqver=3.1.4

    to this:
    vmreqver=7.1.5
    plreqver=3.1.5

    3. mkdir /tmp/vmware && cd /tmp/vmware
    cp -R /usr/lib/vmware/modules/source/ .
    cd /tmp/vmware/source

    4. From root terminal, copied both the
    vmware2.6.39patchv3.tar.bz2 & vmware2.6.39fixedv3.patch files to
    /tmp/vmware/source

    5. for i in ./*.tar; do tar -xf $i; done
    for i in ./*.tar; do mv $i $i.orginal; done

    6. patch -t -f -p1 < vmware2.6.39fixedv3.patch
    when you run the above, you should see patching file proceed

    7. Then issued the following;

    tar cf vmblock.tar vmblock-only
    tar cf vmci.tar vmci-only
    tar cf vmmon.tar vmmon-only
    tar cf vmnet.tar vmnet-only
    tar cf vsock.tar vsock-only

    8. cp -vf *.tar /usr/lib/vmware/modules/source/

    9. Open VMware Workstation, ran like a charm.

    Again thanks for Weltall for going to the effort to create the patch, much appreciated.

    Regards,

    powderskier9

  90. powderskier9 and Weltall – I’m very grateful for your help!

    Spent hours looking for this fix. Completed in a few minutes with these patches!

    Ubuntu 10.04
    3.0.0-16-generic-pae
    Vmware 7.1.5

  91. [...] referencia… Post original aquí *{margin:0; padding:0;} ul{ list-style:none;} #socialbuttonnav {width:90%; [...]

  92. [...] I don’t understand why vmware7.1.X do not support the new Linux kernel. It stucks at starting phase when trying to build kernel modules. But when we really want to run it, there is a way. Download the patches post here http://weltall.heliohost.org/wordpress/2011/05/14/running-vmware-workstation-player-on-linux-2-6-39-… [...]

  93. Is there another solution other than a V8 upgrade?

    diebelr@ubuntu:/tmp/vmware/source$ patch -t -f -p1 < vmware2.6.39fixedv3.patch
    patching file vmblock-only/linux/dentry.c
    patching file vmblock-only/linux/filesystem.c
    can't find file to patch at input line 109
    Perhaps you used the wrong -p or –strip option?
    The text leading up to this was:
    ————————–
    |diff -u -r source-orig/vmci-only/linux/driver.c source/vmci-only/linux/driver.c
    |— source-orig/vmci-only/linux/driver.c 2011-03-26 06:37:32.000000000 +0100
    |+++ source/vmci-only/linux/driver.c 2011-04-02 13:32:12.000000000 +0200
    ————————–
    No file to patch. Skipping patch.
    1 out of 1 hunk ignored
    can't find file to patch at input line 120
    Perhaps you used the wrong -p or –strip option?
    The text leading up to this was:
    ————————–
    |diff -u -r source-orig/vmmon-only/linux/driver.c source/vmmon-only/linux/driver.c
    |— source-orig/vmmon-only/linux/driver.c 2011-03-26 06:37:28.000000000 +0100
    |+++ source/vmmon-only/linux/driver.c 2011-04-02 13:26:59.000000000 +0200
    ————————–
    No file to patch. Skipping patch.

    ~~~~~~~~ continues ~~~~~~~~~~

    • porting by hand the patches. they are mostly similar. Someone did a patch for 7 versions in th more recent posts but it doesn’t cover the very last kernel.

  94. I have an old 32bit laptop computer, I loaded Linux Mint 12

    Linux tirtho-mint 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:50:42 UTC 2011 i686 i686 i386 GNU/Linux

    I used your v3 patch to get my 7.1.5 vmware workstation working but edited

    vmreqver=7.1.4

    to:

    vmreqver=7.1.5

    compiled fine:

    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 done
    Virtual ethernet done
    Shared Memory Available done

    All done, you can now run VMWare WorkStation.
    Modules sources backup can be found in the ‘/usr/lib/vmware/modules/source-workstation7.1.5-2012-05-10-01:42:32-backup’ directory

    just wanted to say thank you for your hard work here!

  95. Patched Ubuntu 12.04 – Linux 3.2.0-24-generic #39-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux
    Vmware 7.15 using patch at http://weltall.heliohost.org/wordpress/2012/01/26/vmware-workstation-8-0-2-player-4-0-2-fix-for-linux-kernel-3-2-and-3-3/

    via comment #44 successfully (again)

  96. [...] some fellow sysadmin from elsewhere patched the old, outdated, crappy vmware tools and another one ported the patches so they could compile on [...]

  97. The script complained that the message:
    /usr/lib/vmware/modules/source/.patched found. You have already patched your sources. Exiting

    .patched exists due to a similar patch I had done on a previous version of Ubuntu
    The solution was not to simply delete the .patched file but to revert to the source as when vmware was first installed.
    1. cd /usr/lib/vmware/modules/
    2. Save source folder to a new backup : mv source source-workstation7.1.5-2012-06-28-17\:08\:23-backup
    3. Restore the original source folder from backup : cp -r source-workstation7.1.5-2011-11-29-01\:07\:23-backup source
    4. run script
    Success!

  98. [...] a este post pude compilar los modulos de vmware 7.1.4 con el ultimo RC de linux [...]

 Leave a Reply

(required)

(required)

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>