VMware Communities
Krellan
Enthusiast
Enthusiast

Here is patch for Workstation 6.5.2 on Linux 2.6.31 kernel

I'm pleased to announce an updated patch. I found some more time to work on it, and there's two big improvements:

1) It's "universal". It works for Linux 2.6.29, and Linux 2.6.30, and Linux 2.6.31!

2) Your VMware module files no longer need to be restored from backup, after a failed upgrade. The patch script is now much smarter about backing up the files that it changes. It uses checksums to make sure that it is seeing the original VMware Workstation 6.5.2 files, and when those files are found, it backs them up to a place that it uses for all future runs. The script is now idempotent: it's OK to run it more than once, it will have the same effect.

Here are 2 files, attached.

There's the shell script, and the patch file.

Download both of these files, to the same directory.

Then, run the script, as root. (Check it first, unless you REALLY trust me not to put some kind of rootkit in there!)

su <-- become root

bash ./vmware-6.5.2-newkernmods.sh <-- run the script

I tested it, and it worked, on these 3 kernels:

Linux 2.6.29.2

Linux 2.6.30.1

Linux 2.6.31-rc3

This is only for VMware Workstation 6.5.2. It won't work on any older version.

It's only for the host OS. It won't work on the guest OS (VMWare Tools).

It won't work on VMware Player.

It won't work on VMware Server.

Do let me know if this works successfully for you!

Reply
0 Kudos
91 Replies
ayates
Contributor
Contributor

null

Reply
0 Kudos
ayates
Contributor
Contributor

Reply
0 Kudos
ayates
Contributor
Contributor

null

Reply
0 Kudos
dibl
Enthusiast
Enthusiast

Yes, that fixed it on my Kubuntu 9.10 installation (adding the line to /etc/vmware/bootstrap). Thanks!

Reply
0 Kudos
theooze
Contributor
Contributor

Workstation 6.5.3 seems to work will on 2.6.30.5-43.fc11.x86_64. The only thing not working is sound in the guests.

Reply
0 Kudos
nightingale1
Contributor
Contributor

Hello, i NEVER patched something before.

Could anybody explain me step by step how i aply this patch.

Thanks a lot.

Thanks my question was answerd.

Reply
0 Kudos
anja98
Contributor
Contributor

Your patch is great!

Was experiencing vmware kernel upgrade problems after upgrading my Ubuntu Jaunty to the Ubuntu Karmic test build.

Your patch solves it

Reply
0 Kudos
geeksmith
Contributor
Contributor

I applied the patch to Ubuntu 9.10 running kernel 2.6.31-13-generic 32-bit and vmware server 2.0.1-156745.i386. For some reason the line numbers in the patch were always a few lines off, so I applied the patch manually and saved my tarballs. Working great! Thanks for your efforts! If anybody's interested in the patch for 32-bit that worked for me, let me know and I'll take the time to make one that works with the original author's install script.

@@ron

Reply
0 Kudos
pcampbell
Contributor
Contributor

i need a patch for esx 3.5 tools for guest gentoo kernel 2.6.30

does anyone have one?

thanks!

Reply
0 Kudos
SILLAT
Contributor
Contributor

THANK YOU VERY MUCH

I'M RUNNING UBUNTU KARMIC 9.10 RC WORKING GREAT WITH THE UPDATED PATCH MODULE

I'M RUNNING UBUNTU KARMIC 9.10 RC AND I WAS HAVING PROBLEMS INSTALLING VMWARE, I WAS ALSO HAVING MD5 CHECKSUM HASH PROBLEMS WITH THE PREVIOUS PATCES POSTED EARLIER BUT THIS NEW UPDATED MODULE SEEM TO RUN JUS FINE.

THANKS

Reply
0 Kudos
yojon
Contributor
Contributor

Guys-

Am trying to apply Krellan's patch from July 17 and shell script from July 19 to a fresh install of 64 bit Workstation 6.5.3 on an FC11 installation of kernel 2.6.30.8.64.fc11.x86_64.

Unfortunately, I am getting the checksum errors:

root@archie Download# bash ./vmware-6.5.2-newkernmods.sh

Sorry, installed file content does not match what was expected

for VMware Workstation 6.5.3 /usr/lib/vmware/modules/source/vmblock.tar file.

Your checksum: 583aa0af933d8e4cf33ac3c1aa140d24

Expected checksum (64-bit): 08894c1edd8c7c1c45846768102f3700

Expected checksum (32-bit): 111725518eb37a65e5ad6bc6bd16774b

Am I missing something obvious??

Thanks!

Reply
0 Kudos
dibl
Enthusiast
Enthusiast

kernel 2.6.3_0_.8.64.fc11.x86_64.

Looks like the wrong patch.

Reply
0 Kudos
flashbackpa
Contributor
Contributor

You have wrong MD5 values, in the original files those values are referred to vmware 6.2, you should change them for you 6.3 version..

use the md5sum command to caluclate new values and overwrite the old values in the script.

After my wise comment, i tried to apply the patch and this is the (poor) result:

./vmware-6.5.3-newkernmods.sh

Found pristine /usr/lib/vmware/modules/source/vmblock.tar

Backing it up to /usr/lib/vmware/modules/source/vmblock.tar.backup-6.5.3

Found pristine /usr/lib/vmware/modules/source/vmci.tar

Backing it up to /usr/lib/vmware/modules/source/vmci.tar.backup-6.5.3

Found pristine /usr/lib/vmware/modules/source/vmmon.tar

Backing it up to /usr/lib/vmware/modules/source/vmmon.tar.backup-6.5.3

Found pristine /usr/lib/vmware/modules/source/vmnet.tar

Backing it up to /usr/lib/vmware/modules/source/vmnet.tar.backup-6.5.3

Found pristine /usr/lib/vmware/modules/source/vsock.tar

Backing it up to /usr/lib/vmware/modules/source/vsock.tar.backup-6.5.3

Found backup /usr/lib/vmware/modules/source/vmblock.tar.backup-6.5.3

Restoring it to /usr/lib/vmware/modules/source/vmblock.tar

Unpacking /usr/lib/vmware/modules/source/vmblock-only

Found backup /usr/lib/vmware/modules/source/vmci.tar.backup-6.5.3

Restoring it to /usr/lib/vmware/modules/source/vmci.tar

Unpacking /usr/lib/vmware/modules/source/vmci-only

Found backup /usr/lib/vmware/modules/source/vmmon.tar.backup-6.5.3

Restoring it to /usr/lib/vmware/modules/source/vmmon.tar

Unpacking /usr/lib/vmware/modules/source/vmmon-only

Found backup /usr/lib/vmware/modules/source/vmnet.tar.backup-6.5.3

Restoring it to /usr/lib/vmware/modules/source/vmnet.tar

Unpacking /usr/lib/vmware/modules/source/vmnet-only

Found backup /usr/lib/vmware/modules/source/vsock.tar.backup-6.5.3

Restoring it to /usr/lib/vmware/modules/source/vsock.tar

Unpacking /usr/lib/vmware/modules/source/vsock-only

Testing patch

patching file vmblock-only/linux/control.c

Hunk #2 FAILED at 158.

Hunk #3 FAILED at 172.

2 out of 3 hunks FAILED -- saving rejects to file vmblock-only/linux/control.c.rej

patching file vmblock-only/Makefile

Hunk #1 FAILED at 122.

1 out of 1 hunk FAILED -- saving rejects to file vmblock-only/Makefile.rej

patching file vmci-only/Makefile

Hunk #1 FAILED at 122.

1 out of 1 hunk FAILED -- saving rejects to file vmci-only/Makefile.rej

patching file vmmon-only/include/x86svm.h

patching file vmmon-only/linux/driver.c

Hunk #1 FAILED at 1984.

1 out of 1 hunk FAILED -- saving rejects to file vmmon-only/linux/driver.c.rej

patching file vmmon-only/linux/hostif.c

Hunk #2 FAILED at 3538.

Hunk #3 FAILED at 3662.

2 out of 3 hunks FAILED -- saving rejects to file vmmon-only/linux/hostif.c.rej

patching file vmmon-only/Makefile

Hunk #1 FAILED at 122.

1 out of 1 hunk FAILED -- saving rejects to file vmmon-only/Makefile.rej

patching file vmnet-only/Makefile

Hunk #1 FAILED at 122.

1 out of 1 hunk FAILED -- saving rejects to file vmnet-only/Makefile.rej

patching file vmnet-only/netif.c

Hunk #1 FAILED at 194.

Hunk #2 succeeded at 175 (offset -45 lines).

Hunk #3 FAILED at 295.

Hunk #4 FAILED at 541.

Hunk #5 FAILED at 597.

Hunk #6 FAILED at 658.

5 out of 6 hunks FAILED -- saving rejects to file vmnet-only/netif.c.rej

patching file vsock-only/Makefile

Hunk #1 FAILED at 122.

1 out of 1 hunk FAILED -- saving rejects to file vsock-only/Makefile.rej

Sorry, validation of the patch has failed.

Check VMware product name: only Workstation is supported (for now).

Check VMware Workstation version: only 6.5.3 is supported (for now)

Anybody willing to help ?

Thanks ! :smileyblush:

Reply
0 Kudos
flashbackpa
Contributor
Contributor

i'm using a pae kernel ? Is PAE a problem for vmware ? Thanks !

Reply
0 Kudos
martyfelker
Enthusiast
Enthusiast

I have not had to use the patch on any host/gurest setup I have tried. Naturally I haven't tried every one but 6.5.3 has compiled and runs on Ubuntu 9.04, Ubuntu, Slackware 13.0, and Sabayon 4.2 hosts Windows 7 and Windows 2008 Server R2 and Gentoo. Not surprisingly v 6.5.3 has no probables opening VM's created with 6.5.2. This thread is lenghty and I haven't searched all of it to determine if anybody had a specific problem with a particular host/gues. It would appear to me that VMware "probably" fixed this annoyance in 6.5.3 but of course thir is no way to find out for sure unless they 'fess up! In any event, since this is a free upgrade and a free trial I don't see why you would not try using v 6.5.3 of WS.

Marty Felker

Marty Felker
Reply
0 Kudos
0zn0g
Contributor
Contributor

Very nice work...dude you rock!

Reply
0 Kudos
lucasrangit
Contributor
Contributor

What makes VMware tools for VMware Workstation different from VMware tools for ESXi?

Has anyone used this patch with ESXi 4's latest vmware-tools or used the ESXi vmware-tools 2.6.29 patch at http://communities.vmware.com/thread/220312?tstart=0?

Reply
0 Kudos
maestrodata
Contributor
Contributor

Hi,

I installed VMware Workstation 7.0.0 on Ubuntu 9.10 x86_64, with a kernel.org 2.6.32 kernel.

7.0.0 installed after removing 6.5.2 completely, which was patched with one of your great patches, and was actually working fine till I decided to upgrade to 7.0.0

The post-install startup was as follows:

COMPILED - Virtual Machine Monitor

FAILED - Virtual Network Device - FAILED

COMPILED - VMware Blocking Filesystem

FAILED - Virtual Machine Communication Interface

FAILED - VMCI Sockets

Any patch for Linux 2.6.32 on x86_64?

Thanks in advance for all your excellent work!!

Tim

Reply
0 Kudos
martyfelker
Enthusiast
Enthusiast

Somehow I mus have changed the thread concerning the great patch for WS 6.52. Please understand I didn't write it ( could not ever do such programming) but I have sure used it - until 6.53 which didn't have the same istallation problems. I'm using both x64 and x386 machines with various OS - including Ubuntu 9.10.

That being said it looks like your problem is network related - perhaps if you changed from NAT to Bridged or vice versa that "may" help. Uninstall 7.0 using the new command line Installer which includes an uninstalling option -its t in /usr/bin - the old one is deprecated.Then try re-installing 7.0 using the GUI. Only a wild and uniformed guess.

Marty Felker

Marty Felker
Reply
0 Kudos