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:
http://communities.vmware.com//thread/202340
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:
bash ./vmware-6.5.2-modules-2.6.29-fix.sh
It should now apply cleanly, and there should be no errors.
Hope this helps!
Josh
yeah, this is real great jobs, it's worked perfect and without any fail or error.
==============================================
$ patch -N -p1 < vmware-6.5.2-modules-2.6.29-fix.patch
patching file vmblock-only/Makefile
patching file vmci-only/Makefile
patching file vmmon-only/include/x86apic.h
patching file vmmon-only/linux/driver.c
patching file vmmon-only/linux/hostif.c
patching file vmmon-only/Makefile
patching file vmnet-only/Makefile
patching file vmnet-only/netif.c
patching file vsock-only/Makefile
===============================================
Thank you a lot, works great....
Thanks for this- it's unfortunate it's necessary, considering 2.6.29 came out a week before the 6.5.2/156735 release.
Patches for 2.5.2 tested and working perfectly on vmplayer 2.5.2, 2.6.29 kernel, 32 and 64 bit.
Thanks a lot for your efforts on this, much appreciated.
I was hoping someone had made a patch for 2.6.29. One question, this patch only affects the vmware kernel modules right? I doesn't actually affect the kernel or the kernel modules that came with my distros?
Thank you very much, nice job that works perfectly !
Yes, the patch only affects VMware's kernel modules on the host, which are in this directory:
/usr/lib/vmware/modules
It shouldn't affect your distro's kernel or your distro's modules at all.
Josh
Thanks for all your work Josh. Worked like a charm on slackware with kernel 2.6.29.1 and workstation 6.5.2.
--Troy
Worked great in sabayon 4.1 with a 2.6.29 kernel. Now all I need to do is figure out how to make the modules persistant, but that's for another thread.
Thanks for the nicely written patch and clear instruction. One question though, in what way does the ".../modules/binary" directory confuse VMware? (I haven't moved/renamed it in my installation and it works perfectly)
Kind Regards
Andreas
Hi folks, first let me apologize for posting about VMware Tools in the Workstation thread, but I don't see a separate area for Tools, and I modified Krellan's work to use it to install VMware Tools-7.7.5-156745 in the guest OS running kernel 2.6.29. If there is a better area to post this please let me know.
You can get the patch files & script here
Thanks to Krellan and the others for their prior work!
Thank you very much for this patch, i use it on archlinux and it works great.
Keep up the good work.
bye
You're welcome!
Interesting. I haven't yet tried to run Linux 2.6.29 as guest, only as host. (The reason I upgraded to 2.6.29 is to get better hardware support for my motherboard's sensors, which are a moot point in a virtual machine.)
Glad to know the patch (with some modifications) also works as guest.
Josh
As for the modules/binary directory confusing VMware and thus needing to be moved out of the way, this fix might not be needed anymore.
I originally saw it in some older instructions (I forget where), and it seemed like a good idea to follow, at the time. I think there might have been a problem with VMware not doing a full rebuild from source if it found a "supported" kernel version inside of the modules/binary directory, and thus missing some changes that were made in some patches.
At any rate, if it worked successfully for you without needing to move the modules/binary directory out of the way, that's perfectly fine.
Josh