vmware-config.pl:

None of the pre-built vsock modules for VMware Server is suitable for your
running kernel. Do you want this program to try to build the vsock module for
your system (you need to have a C compiler installed on your system)? yes
Extracting the sources of the vsock module.
Building the vsock module.
Using 2.6.x kernel build system.
make: Entrando no diretório `/tmp/vmware-config18/vsock-only'
make -C /lib/modules/2.6.26.2/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entrando no diretório `/home/me/kernel/2.6.26.2'
make -C /usr/src/linux-2.6.26.2 O=/home/me/kernel/2.6.26.2/. modules
CC [M] /tmp/vmware-config18/vsock-only/linux/af_vsock.o
CC [M] /tmp/vmware-config18/vsock-only/linux/driverLog.o
CC [M] /tmp/vmware-config18/vsock-only/linux/util.o
CC [M] /tmp/vmware-config18/vsock-only/linux/vsockAddr.o
LD [M] /tmp/vmware-config18/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: "VMCIDatagram_CreateHnd" [/tmp/vmware-config18/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_DestroyHnd" [/tmp/vmware-config18/vsock-only/vsock.ko] undefined!
WARNING: "VMCI_GetContextID" [/tmp/vmware-config18/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_Send" [/tmp/vmware-config18/vsock-only/vsock.ko] undefined!
CC /tmp/vmware-config18/vsock-only/vsock.mod.o
LD [M] /tmp/vmware-config18/vsock-only/vsock.ko
make[1]: Saindo do diretório `/home/me/kernel/2.6.26.2'
cp -f vsock.ko ./../vsock.o
make: Saindo do diretório `/tmp/vmware-config18/vsock-only'
Unable to make a vsock module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config18/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.
http:// Press the Enter key to continue.

I tried these workarounds but no success:

• http://kramfs.com/2008/07/13/vmware-server-2-unable-to-build-the-vsock-module/
• http://d.hatena.ne.jp/adsaria/searchdiary?word=Module

What to do? rollback to 2.4x kernel?

Ubuntu 8.10 | Linux 2.6.27-7-server #1 SMP x86_64 GNU/Linux

VMware-server-2.0.0-122956.x86_64

I tried this two links without success too.

http://kramfs.com/2008/07/13/vmware-server-2-unable-to-build-the-vsock-module/

http://www.huschi.net/33_310_de.html

Someone already got it running?

-Markus

xkeymap.keycode.108 = 0x138 # Alt_R
xkeymap.keycode.106 = 0x135 # KP_Divide
xkeymap.keycode.104 = 0x11c # KP_Enter
xkeymap.keycode.111 = 0x148 # Up
xkeymap.keycode.116 = 0x150 # Down
xkeymap.keycode.113 = 0x14b # Left
xkeymap.keycode.114 = 0x14d # Right
xkeymap.keycode.105 = 0x11d # Control_R
xkeymap.keycode.118 = 0x152 # Insert
xkeymap.keycode.119 = 0x153 # Delete
xkeymap.keycode.110 = 0x147 # Home
xkeymap.keycode.115 = 0x14f # End
xkeymap.keycode.112 = 0x149 # Prior
xkeymap.keycode.117 = 0x151 # Next
xkeymap.keycode.78 = 0x46 # Scroll_Lock
xkeymap.keycode.127 = 0x100 # Pause
xkeymap.keycode.133 = 0x15b # Meta_L
xkeymap.keycode.134 = 0x15c # Meta_R
xkeymap.keycode.135 = 0x15d # Menu

Still Im waiting a solution for logon VMWARE SERVER 2 on Linux kernel 2.6.26.2 ...