Here we go again, with VMware Workstation 6.5.2 (including VMware Player 2.5.2).
Here is a patch to get their modules to cleanly build on Linux kernel version 2.6.29.
It's a followup from this earlier thread, that was for the earlier 6.5.1 version:
The changes between 6.5.1 and 6.5.2 are minimal. VMware, thankfully, no longer attempts to re-define the APIC_BASE_MSR symbol, making one part of the patch no longer necessary on 2.6.29, so it has been removed. That was what was causing the earlier error: the patch was attempting to patch something that no longer existed in the code.
Here's the new 6.5.2 patch, and a shellscript to help you apply it, attached.
Make sure your /usr/lib/vmware/modules/source directory is pristine. Reinstall 6.5.2 if you have to, in order to return this directory to its unchanged settings, if you had trouble applying the patch earlier.
Use the bash command to run the script:
It should now apply cleanly, and there should be no errors.
Hope this helps!
I attempted the patch for 6.5.2 to Linux kernel 2.6.29 with similar results everyone else was or is experiencing. I do realize Fedora 11 is on the outer edge and such, but this doesn't seem to difficult conceptually. If you have a suggestion it is appreciated. Thanks.
The command bash ./vmware-6.5.2-modules-2.6.29-fix.sh with the results as follows:
Found tar file for vmnet module
Found tar file for vmmon-temp module
Found tar file for vmci module
Found tar file for vmblock-temp module
Found tar file for vmppuser-temp module
Found tar file for vmblock module
Found tar file for vmnet-temp module
Found tar file for vmppuser module
Found tar file for vmmon module
Found tar file for vmci-temp module
Found tar file for vsock-temp module
Found tar file for vsock module
Using patch file: /home/sdouglas/Download/vmware-6.5.2-modules-2.6.29-fix.patch
Using module directory: /usr/lib/vmware/modules/source
Using backup directory: /usr/lib/vmware/modules/source-backup
Sorry, vmmon-temp.tar tarball failed to extract the directory vmmon-temp-only
Here is a coure of actions I tried ending with the above status as follows:
Installed both the batch and rpm method with the same results
Confidient both the kernel headers and gcc are updated
My system specifications are as follows:
Kernel Linux 22.214.171.124-191.fc11.i586
2.8 GB RAM
2.8 Ghz CPU (2)
Ran the command "patch -N -p1 < vmware-6.5.2-modules-2.6.29-fix.patch" with results as follows:
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -urN source-OLD/vmblock-only/Makefile source-NEW/vmblock-only/Makefile
|--- source-OLD/vmblock-only/Makefile 2009-03-26 22:05:21.000000000 -0700
|+++ source-NEW/vmblock-only/Makefile 2009-04-04 02:17:17.000000000 -0700
File to patch:-----
Message was edited by: stevewd
I had the same problem. I finaly got around it by uninstalling vmware and renaming the /usr/lib/vmware/modules directory (the uninstall didnt clean everything out) then re installing everything. the fix it script wont run on anything but perfictlay clean
install. I did this:
rpm -i VMware-Workstation-6.5.2-156735.i386.rpm
vmware-modconfig --console --install-all
this ran ok then rebooted and try vmware load and it works.
I moved from Fedora to CentOS (RHEL clone). It has full support for my laptop's hardware (Dell Vostro 1400), it's 100% supported by VMware (because it's basically RHEL rebadged) and the best of all: It's not ubuntu!! :D. It's not the latest and greatest software versions, but I prefer stability. I guess I'm getting old :P.
lsper: Unfortunately, I don't have access to VMware Workstation betas, so I can't make a patch for that.
I would like to, though. Been waiting a while for them to fix the Nehalem issues!
If you can pass on some information as to how I can get onto the VMware Workstation beta list, then I'll be glad to see what I can do from there.
the link in your post is stale now. is your patch to make vmware-tools work with the v.2.6.29 kernel running as a guest under
workstation 6.5.2 available somewhere else? or has it been incorporated into one of krellan's excellent patches now?
thanks in advance.
just out of curiosity, why do people prefer to make the tools from vmware work (on a linux guest) rather than use the open-vm-tools package (which is packaged as an rpm at least in FC11)?
I'm out of the office today Tue. 14/07.
I have full access to my emails, and will respond accordingly whenever possible.
For urgent business matter, you can reach me on my mobile phone (+32 486 606090)
Met vriendelijke groeten,
ICT Manager Hamann International Logistics NV
vertegenwoordigd door Peter De Groote
Neem een kijkje op de volledig nieuwe website van Hamann !!
Do have a look at Hamann's totally redesigned website !!
I've posted a new patch, that will work for Linux 2.6.29. It will also work for 2.6.30 and 2.6.31.
It's in this thread:
This new patch now supersedes all of my earlier patches. Hopefully this will solve a lot of problems that people had with the earlier patches.
You might need to restore your VMware Workstation 6.5.2 installation from backup, or at least the /usr/lib/vmware/modules/source directory. The new patch script now looks at the original modules in a much more careful way, and backs them up in a much safer way that can be ran more than once without causing failure. Unfortunately, to do this, I had to make it incompatible with the original script.
So, copy back your /usr/lib/vmware/modules/source directory from backup, or just reinstall VMware Workstation 6.5.2, and you should be OK.
Hope this helps!
I've got following error message:
root@inspiron modules# ./vmware-6.5.2-newkernmods.sh
Sorry, installed file content does not match what was expected
for VMware Workstation 6.5.2 /usr/lib/vmware/modules/source/vmblock.tar file.
Your checksum: 111725518eb37a65e5ad6bc6bd16774b
Expected checksum: 08894c1edd8c7c1c45846768102f3700
Pls can you help me out?
Slavek: That means that the files were not an exact match for what was originally installed, when VMware Workstation 6.5.2 was installed. So, try removing the /usr/lib/vmware/modules directory, then reinstall VMware on top of your old installation. That should replace the files. Make sure your version is exactly VMware Workstation 6.5.2.
I trust that you want follow-ups to your new patch in the new thread. I have added a follow-up there. Looks like I have the same starting point as slavek1979, even after a clean install. (See the follow-up for details in http://communities.vmware.com/thread/221724.)
BTW, thanks for the great work.
I couldn't figure out what was wrong, until I found your post, then applied your patch, and it's magic. Vmware should be paying you for the work you've done to make their fee based application work. I was thinking about switching to VirtualBox until I found your patch! Thanks!