By popular demand, here is an update of my original patch. It now works on 2.6.30 (I tested on 2.6.30-rc4). I'm using VMware Workstation 6.5.2.
This patch runs exactly the same as my earlier 2.6.29 patch script, which was here:
http://communities.vmware.com//thread/203231
The instructions are exactly the same as before. Download the patch, and also, download the script to help you apply it. There should be 2 attachments to this message.
Use the bash command to run the script, as root. (Look at the script first, so you know I didn't put something nasty in it!):
bash ./vmware-6.5.2-modules-2.6.30-fix.sh
It should now apply cleanly, and there should be no errors.
If there were errors, please restore your original VMware modules from backup. If you earlier tried the 2.6.29 patch script, and it failed because you're running the 2.6.30 kernel, then you'll need to undo my previous patch before trying this patch. Here's the command that will restore your earlier VMware modules:
cp -v /usr/lib/vmware/modules/source-backup/* /usr/lib/vmware/modules/source
This will restore your modules to their earlier pristine condition (hopefully), and you can now try again to run the 2.6.30 script.
I tried this and it works to run my virtual machines under 2.6.30. There are very few changes between 2.6.29 and 2.6.30 from VMware's point of view, which makes it minimally invasive. Let me know how this works.
Josh
This patch runs exactly the same as my earlier 2.6.29 patch script, which was here:
http://communities.vmware.com//thread/203231
The instructions are exactly the same as before. Download the patch, and also, download the script to help you apply it. There should be 2 attachments to this message.
Use the bash command to run the script, as root. (Look at the script first, so you know I didn't put something nasty in it!):
bash ./vmware-6.5.2-modules-2.6.30-fix.sh
It should now apply cleanly, and there should be no errors.
If there were errors, please restore your original VMware modules from backup. If you earlier tried the 2.6.29 patch script, and it failed because you're running the 2.6.30 kernel, then you'll need to undo my previous patch before trying this patch. Here's the command that will restore your earlier VMware modules:
cp -v /usr/lib/vmware/modules/source-backup/* /usr/lib/vmware/modules/source
This will restore your modules to their earlier pristine condition (hopefully), and you can now try again to run the 2.6.30 script.
I tried this and it works to run my virtual machines under 2.6.30. There are very few changes between 2.6.29 and 2.6.30 from VMware's point of view, which makes it minimally invasive. Let me know how this works.
Josh
Attachments:
- vmware-6.5.2-modules-2.6.30-fix.sh (3.4 K)
- vmware-6.5.2-modules-2.6.30-fix.patch (10.8 K)
