vmware-an..specific-specific 5.5.7 and kernel 2.6.26
Posted on July 24th, 2008
You can follow any responses to this entry through the RSS 2.0 feed.
It’s getting harder and harder to just sit back and enjoy the finest things in.. no =( Harder and harder to find updates like vmware-any-any-updateXXX for vmware 5.5.x – actually, you can probably only find updates for vmware 6.x at the moment.
That’s why, any-any doesn’t make sense anymore. It’s really kernel version specific and vmware version specific at the moment. So if you use vmware 5.5.7 and the latest 2.6.26 linux kernel here’s the patch i just made:
September 24th, 2008 at 6:20 pm
THANK YOU!!!!!!!!!!
October 9th, 2008 at 9:03 pm
Thank you, Thank you, Thank you!
October 12th, 2008 at 9:31 pm
Thanks, works for my 5.5.1 too, hope will works for 2.6.27 too, have seen comments with new problem with that new kernel.
October 13th, 2008 at 5:50 pm
I’m soon upgrading to 2.6.27 so i’ll post a fix for this kernel as well if necessary. (and if no one cared to do it first)
October 20th, 2008 at 3:46 pm
So yeah, I updated to 2.6.27 and quite a few changes were necessary.
Please see http://www.insecure.ws/2008/10/20/vmware-specific-specific-55x-and-kernel-2627 for the updated patch, good luck
November 11th, 2008 at 4:41 am
Hi, is possible to patch my kernel (2.6.26.2) for VMware Server 2 or 1.0.8?
I am looking one way to fix it but only a few sites but them doesn’t have a valid solution for that..
Thanks you.
November 11th, 2008 at 4:43 am
Here is the error:
Building the vsock module.
Using 2.6.x kernel build system.
make: Entrando no diretório `/tmp/vmware-config32/vsock-only’
make -C /lib/modules/2.6.26.2-pow/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entrando no diretório `/home/powtrix/kernel/2.6.26.2′
make -C /usr/src/linux-2.6.26.2 O=/home/powtrix/kernel/2.6.26.2/. modules
CC [M] /tmp/vmware-config32/vsock-only/linux/af_vsock.o
CC [M] /tmp/vmware-config32/vsock-only/linux/driverLog.o
CC [M] /tmp/vmware-config32/vsock-only/linux/util.o
CC [M] /tmp/vmware-config32/vsock-only/linux/vsockAddr.o
LD [M] /tmp/vmware-config32/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: “VMCIDatagram_CreateHnd” [/tmp/vmware-config32/vsock-only/vsock.ko] undefined!
WARNING: “VMCIDatagram_DestroyHnd” [/tmp/vmware-config32/vsock-only/vsock.ko] undefined!
WARNING: “VMCI_GetContextID” [/tmp/vmware-config32/vsock-only/vsock.ko] undefined!
WARNING: “VMCIDatagram_Send” [/tmp/vmware-config32/vsock-only/vsock.ko] undefined!
CC /tmp/vmware-config32/vsock-only/vsock.mod.o
LD [M] /tmp/vmware-config32/vsock-only/vsock.ko
make[1]: Saindo do diretório `/home/powtrix/kernel/2.6.26.2′
cp -f vsock.ko ./../vsock.o
make: Saindo do diretório `/tmp/vmware-config32/vsock-only’
Unable to make a vsock module that can be loaded in the running kernel:
insmod: error inserting ‘/tmp/vmware-config32/vsock.o’: -1 Unknown symbol in module
There is probably a slight difference in the kernel configuration between the
set of C header files you specified and your running kernel. You may want to
rebuild a kernel based on that directory, or specify another directory.
The VM communication interface socket family is used in conjunction with the VM
communication interface to provide a new communication path among guests and
host. The rest of this software provided by VMware Server is designed to work
independently of this feature. If you wish to have the VSOCK feature you can
install the driver by running vmware-config.pl again after making sure that
gcc, binutils, make and the kernel sources for your running kernel are
installed on your machine. These packages are available on your distribution’s
installation CD.
[ Press the Enter key to continue.] ^C
January 19th, 2009 at 1:27 pm
Thanx,
Worked fine with server 1.0.4 as well and fixes the “version mismatch vmmon module expecting 138,0 got 168.0″ problem as well !
February 16th, 2009 at 7:52 pm
Yes, it worked for me too to solve the “version mismatch vmmon module expecting 138,0 got 168.0″ on my updated Debian Lenny! Thanks a lot!
March 7th, 2009 at 8:52 am
Thanx,
It work very mutch!
I try before any-any on, debian lenny 2.6.26-1 vmware server 1.0.8
I got “version mismatch vmmon module expecting 138,0 got 168.0″ problem
Thx agan, nice job.
PETER
March 10th, 2009 at 10:18 am
Thank you!
March 14th, 2009 at 8:51 pm
Thank you VERY MUCH for this!
One note for others: when I first installed this and ran vmware-config.pl, I got the error message
error trying to exec ‘cc1plus’: execvp: No such file or directory
This means you need to install the g++ compiler. (I had gcc but not g++.) Once that was installed, it worked great!
March 26th, 2009 at 4:41 pm
[...] aptitude install ia32-libs 如果是32位系统，这个就可以省了 5.http://www.insecure.ws/2008/07/24/vmware-anspecific-specific-557-and-kernel-2626 下载 vmware-update-2.6.26-5.5.7.gz这个附件 6.tar xvf VMware-server-1.0.8-126538.tar.gz tar [...]
April 1st, 2009 at 12:23 am
sorry, not on my system
any ideas?
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config4/vmmon-only’
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.26-1-686′
CC [M] /tmp/vmware-config4/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config4/vmmon-only/linux/driverLog.o
CC [M] /tmp/vmware-config4/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config4/vmmon-only/common/comport.o
CC [M] /tmp/vmware-config4/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config4/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config4/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config4/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config4/vmmon-only/common/task.o
gcc-4.1: error trying to exec ‘cc1plus’: execvp: Datei oder Verzeichnis nicht gefunden
make[2]: *** [/tmp/vmware-config4/vmmon-only/common/task.o] Fehler 1
make[1]: *** [_module_/tmp/vmware-config4/vmmon-only] Fehler 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686′
make: *** [vmmon.ko] Fehler 2
make: Leaving directory `/tmp/vmware-config4/vmmon-only’
Unable to build the vmmon module.
For more information on how to troubleshoot module-related problems, please
visit our Web site at “http://www.vmware.com/download/modules/modules.html” and
“http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html”.
Execution aborted.
debian:~/vmware-update-2.6.26-5.5.7#
July 5th, 2009 at 2:23 am
It worked for vmware 1.0.9 and linux 2.6.26. Thanks!
It seem every time I upgrade vmware I end up in a panic when the kernel modules don’t compile. Why can’t vmware get their act together?
November 5th, 2009 at 2:36 am
Thank you, thank you
Vmware WS 5.5.9 and Debian Lenny (kernel 2.6.26)+vmware-update-2.6.26-5.5.7. Spews a few errors during config.pl, it works though.
I have been using kernel 2.6.18 + WS 5.5.4 for ‘quite some time’ and was glad to find a way to ‘modernize’ a legacy piece of software.
December 9th, 2009 at 8:56 am
It’s not working, unfortunately. (expected v138, got v137)
Debian Lenny 5.0.3 with Kernel 2.6.26(-2-686) and VMware Server 1.0.9 or 1.0.10
For full details see:
http://pastebin.com/f8c10b0e
December 9th, 2009 at 1:31 pm
Hi Mark,
unfortunately this means your vmware version is more recent than the pach (the patch works fine)
However.. maybe you have ws 5.5 scripts (or binary) and server 1.x at the same time or something?
Here’s vmmon version table:
#define VMMON_VERSION_GSX1 (3 << 16 | 0)
#define VMMON_VERSION_V3 (8 << 16 | 0)
#define VMMON_VERSION_V32 (10 << 16 | 0)
#define VMMON_VERSION_GSX2 (21 << 16 | 0)
#define VMMON_VERSION_V321 (30 << 16 | 0)
#define VMMON_VERSION_GSX25 (41 << 16 | 0)
#define VMMON_VERSION_GSX251 (42 << 16 | 0)
#define VMMON_VERSION_V4 (52 << 16 | 0)
#define VMMON_VERSION_V45 (79 << 16 | 0)
#define VMMON_VERSION_V452 (81 << 16 | 0)
#define VMMON_VERSION_GSX32 (85 << 16 | 0)
#define VMMON_VERSION_V5 (116 << 16 | 0)
#define VMMON_VERSION_V55 (137 << 16 | 0)
#define VMMON_VERSION_S1B1 (138 << 16 | 0)
#define VMMON_VERSION_V6 (161 << 16 | 0)
S1B1 is correct and is 138. 137 is ws 5.5
This is the part that detect vmware version running:
switch (iocmd) {
case IOCTL_VMX86_S1B1_VERSION:
return VMMON_VERSION_S1B1;
December 12th, 2009 at 3:23 am
Let me do a little debugging here:
To get VMMON_VERSION_V55 we must be in LinuxDriver_IoctlV55(), in
driver_compat2.h, since that is the only place where it occurs.
I don’t know how we get there but it says
case IOCTL_VMX86_S1B1_VERSION:
return VMMON_VERSION_V55;
which seems strange to me…, do you agree?
To get there we must have case VME_V55 in “switch (vmLinux->version)” in
LinuxDriver_Ioctl, also in driver_compat2.h.
We also see that it says “VMware 2 or VMware Express detected, building
for VMware 2, VMware Express and VMware Workstation 4.0.x.” in
getversion.pl, which would be the case for “if (not defined($res)) {”
but which would also yield VME_V4, not VME_V55, so I am a little
confused here…