Thursday, July 17, 2008

How to install VMWare in 2.6.26 linux kernel

As provided in the "Files" section(located here), I have uploaded the NEW vmware-any-any-update117c.tar.gz to compile against Linux Kernel 2.6.26. But first you must edit the .config for your kernel, and change the CONFIG_UNUSED_SYMBOLS to "y", and recompile it, so that there exists a symbol "init_mm" in the vmlinux binary file (objdump -t can see).

Once you recompile the kernel and get your machine up and running, you will want to extract the vmware-any-any-update117c.tar.gz. Once extracted, open the folder to the directory where you see a file called '' and open a Command Line/Terminal in that folder. Now that you have the terminal open, type su, or sudo su, and then enter your computers root password. Next, in the vmware-any-any-update117c directory, type ./ and follow through with the any-any-update script. Once finished, you'll have VMWare configured and working with the 2.6.26 Kernel!

Hope this helps everyone get VMWare working with the Linux Kernel 2.6.26!

I tested this on openSUSE Linux 10.3 (32bit), Kernel 2.6.26, with VMWare Workstation 6.0.4-93057 (newest version at time of writing this article).

You can download the vmware-any-any-update117c.tar.gz package here:

Files Section:

and you'll see the file called 'vmware-any-any-update117c.tar.gz' that I created and uploaded today (Thursday, July 17th 2008).

That's the one you want to download!

VMWare-Any-Any-Update117c.tar.gz - Direct Download Link:

Best Regards,

James (a.k.a. jtrag)


mcgoy said...

Greetings! I do appreciate your helping with this. When I try to start a VM I get: Version mismatch with vmmon module: expecting 138.0, got 168.0

Any ideas about that error?

x said...

Trying to install Vmserver 1.05 on Debian Sid and 2.6.26 I used update117c and changed iocontrols.h VMMON_VERSION to 138 because he complained about its setting.

Then the reinstallation was clean.

But now when I start vmware I get: Not enough physical memory is available to power on this virtual machine

That is strange because I have never had that before with 1.05 and 1.04.

Free shows:
hugo@debian:/sdb1/server-1.0.5-26$ free
total used free shared buffers cached
Mem: 905780 892624 13156 0 48468 576848
-/+ buffers/cache: 267308 638472
Swap: 976712 212 976500

Any ideas?

Hugo Vanwoerkom

pbx06 said...

i have problems:

Unable to open the installer database /etc/vmware/locations in read-mode.

Execution aborted.

ls /etc/vmware/
bootstrap components config database networking vmnet1 vmnet8

i have managed to install the vmware workstatiob 6.5 beta but it doesn not install any modules !

Joe R. said...

Having the same issue as the original poster... using VMWare Server 1.0.6 on Slackware Linux 12.1 using a vanilla kernel (although I had the same issue using the vanilla 2.6.26 kernel as well). VMWare Server starts up fine, but when I attempt to start a virtual machine I get the "expecting 138.0, got 168.0" error. Any idea what I might be able to do to get things working again? Thanks in advance for any help or advice you can provide!

Anonymous said...

There are changes in the proc fs implementation in kernel, and while compiling the vmmemctl module with any-any 117c you get this:

/tmp/vmware-config8/vmmemctl-only/os.c: In function 'os_init':
/tmp/vmware-config8/vmmemctl-only/os.c:590: error: 'struct proc_dir_entry' has no member named 'get_info'


ale said...

I'm experiencing the same problem using a Vanilla kernel, vmware-server-1.0.6, vmware-server-console-1.0.6 and applying any-any 117d patch.
I've also seen the 138-168 mismatch which can be corrected untarring vmmon.tar and retarring it after the modification in iocontrols.h.
After this, I've seen the same "Not enough physical memory is available to power on this virtual machine" but the same virtual machine opens on another machine having less memory.
The kernel also emits an error about an unsupported 2026 ioctl on /dev/vmmon, probably is here the problem.

I'm not so expert in vmware so, if someone knows how to solve the problem, please let me know too. Thanks.

Anonymous said...

Hi, I had the same problem about the version mismatch. I use vmware ws 6.0.2 and it expects 167, so i guess the problem can be solved by upgrading your vmware products. I'll look for a workaround though.

oncethor said...

it works on CentOS 5.2 x86_64, using VMware server 1.0.7.

Thank you!


x said...

oncethor, what does "it" mean? vmserver 1.0.7 works without patches?