1. Устанавливаем пакеты g++-4.1 cpp-4.1 gcc-4.1 linux-headers-2.6.24-1-686 linux-source-2.6.24
Далее
# rm /usr/bin/gcc; rm /usr/bin/g++; rm /usr/bin/cpp; rm /usr/src/linux
#ln -s /usr/bin/gcc-4.1 /usr/bin/gcc; ln -s /usr/bin/g++-4.1 /usr/bin/g++; ln -s /usr/bin/cpp-4.1 /usr/bin/cpp; ln -s /usr/src/linux-source-2.6.24 /usr/src/linux

2. Скачиваем vmware-player на http://www.vmware.com/products/player/ (нужны исходники) и патч к нему http://knihovny.cvut.cz/ftp/pub/vmware/vmware-any-any-update115.tar.gz
Все это хозяйство распаковываем в /usr/src. (См. п. 4 на всякий случай :) )

3. Редактируем патч.
* В /vmware-any-any-update115 распаковываем файл vmmon.tar
* Открываем vmmon-only/include/vcpuset.h и меняем строку #include "asm/bitops.h" на #include "linux/bitops.h"
* Открываем vmmon-only/include/iocontrols_compat.h и меняем значение VMMONVERSION_V6 на 167
* Открываем vmmon-only/include/iocontrols.h и меняем значение VMMON_VERSION_V6 на 167 (с 20,03,08 не актуально)

----Результаты изменений------------------------------------------------------
diff -ur vmmon-only/include/iocontrols_compat.h
vmmon-only.patched/include/iocontrols_compat.h
--- vmmon-only/include/iocontrols_compat.h 2007-07-23
11:59:47.000000000 +0200
+++ vmmon-only.patched/include/iocontrols_compat.h 2008-01-17
19:41:08.227996503 +0100
@@ -15,7 +15,7 @@
#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)
+#define VMMON_VERSION_V6 (167 << 16 | 0)

/*
* Limit structure for CREATE_VM
diff -ur vmmon-only/include/iocontrols.h
vmmon-only.patched/include/iocontrols.h
--- vmmon-only/include/iocontrols.h 2007-11-28 11:48:50.000000000
+0100
+++ vmmon-only.patched/include/iocontrols.h 2008-01-17
19:41:30.687235832 +0100
@@ -45,7 +45,7 @@
*
*/

-#define VMMON_VERSION (161 << 16 | 0)
+#define VMMON_VERSION (167 << 16 | 0)
#define VMMON_VERSION_MAJOR(v) ((uint32) (v) >> 16)
#define VMMON_VERSION_MINOR(v) ((uint16) (v))

diff -ur vmmon-only/include/vcpuset.h
vmmon-only.patched/include/vcpuset.h
--- vmmon-only/include/vcpuset.h 2007-07-22 13:21:17.000000000
+0200
+++ vmmon-only.patched/include/vcpuset.h 2008-01-17
19:07:34.039175222 +0100
@@ -71,7 +71,7 @@
#define ffs(x) ffs_x86_64(x)

#elif defined MODULE
- #include "asm/bitops.h"
+ #include "linux/bitops.h"
#elif defined __APPLE__ && defined KERNEL
/*
* XXXMACOS An ugly hack to resolve redefinition of PAGE_ defines
-----------------------------------------------------------------------------



* Создаем новый vmmon.tar :
#tar -cf vmmon.tar vmmon-only

4. Запускаем runme.pl который прилагается к патчу. (Но тут есть сомнения! Не исключено, что сначала надо все же запустить /usr/src/vmware-player-distrib/vmware-install.pl, потом уже переходить к пункту 3)




----------------------------------------------------------------------------
Логи установки:
#/usr/src/vmware-any-any-update115/runme.pl
Updating /usr/bin/vmware ... failed
Cannot open /usr/bin/vmware: No such file or directory
Updating /usr/bin/vmnet-bridge ... No patch needed/available
Updating /usr/lib/vmware/bin/vmware-vmx ... No patch needed/available
Updating /usr/lib/vmware/bin-debug/vmware-vmx ... No patch needed/available
VMware modules in "/usr/lib/vmware/modules/source" has been updated.

Before running VMware for the first time after update, you need to configure it
for your running kernel by invoking the following command:
"/usr/bin/vmware-config.pl". Do you want this script to invoke the command for
you now? [yes]

Making sure services for VMware Player are stopped.

Stopping VMware services:
Virtual machine monitor done

Configuring fallback GTK+ 2.4 libraries.

In which directory do you want to install the theme icons?
[/usr/share/icons]

What directory contains your desktop menu entry files? These files have a
.desktop file extension. [/usr/share/applications]

In which directory do you want to install the application's icon?
[/usr/share/pixmaps]

Trying to find a suitable vmmon module for your running kernel.

None of the pre-built vmmon modules for VMware Player is suitable for your
running kernel. Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? [yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux-headers-2.6.24-1-686/include]

Extracting the sources of the vmmon module.

Building the vmmon module.

Unknown VMware Workstation 6.0.2 build 59824 detected. Building for Workstation 6.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config4/vmmon-only'
make -C /usr/src/linux-headers-2.6.24-1-686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.24-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
cc1plus: warning: command line option "-Werror-implicit-function-declaration" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wdeclaration-after-statement" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wno-pointer-sign" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for Ada/C/ObjC but not for C++
cc1plus: warning: command line option "-ffreestanding" is valid for C/ObjC but not for C++
/tmp/vmware-config4/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV321]’:
/tmp/vmware-config4/vmmon-only/common/task_compat.h:2491: warning: ‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:2492: warning: ‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV3]’:
/tmp/vmware-config4/vmmon-only/common/task_compat.h:2491: warning: ‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:2492: warning: ‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageGSX1]’:
/tmp/vmware-config4/vmmon-only/common/task_compat.h:2491: warning: ‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:2492: warning: ‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV2]’:
/tmp/vmware-config4/vmmon-only/common/task_compat.h:2491: warning: ‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:2492: warning: ‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM_V4(VMDriver*, Vcpuid) [with VMCrossPage = VMCrossPageV4]’:
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::rsp’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::rip’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMDriver*, Vcpuid)’:
/tmp/vmware-config4/vmmon-only/common/task_compat.h:2491: warning: ‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:2492: warning: ‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::rsp’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::rip’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::rsp’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::rip’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h: In function ‘void Task_Switch_V45(VMDriver*, Vcpuid)’:
/tmp/vmware-config4/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::rsp’ may be used uninitialized in this function
/tmp/vmware-config4/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::rip’ may be used uninitialized in this function
CC [M] /tmp/vmware-config4/vmmon-only/common/vmciContext.o
CC [M] /tmp/vmware-config4/vmmon-only/common/vmciDatagram.o
CC [M] /tmp/vmware-config4/vmmon-only/common/vmciDriver.o
CC [M] /tmp/vmware-config4/vmmon-only/common/vmciDs.o
CC [M] /tmp/vmware-config4/vmmon-only/common/vmciGroup.o
CC [M] /tmp/vmware-config4/vmmon-only/common/vmciHashtable.o
CC [M] /tmp/vmware-config4/vmmon-only/common/vmciProcess.o
CC [M] /tmp/vmware-config4/vmmon-only/common/vmciResource.o
CC [M] /tmp/vmware-config4/vmmon-only/common/vmciSharedMem.o
CC [M] /tmp/vmware-config4/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config4/vmmon-only/vmcore/compat.o
CC [M] /tmp/vmware-config4/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config4/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config4/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config4/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-1-686'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config4/vmmon-only'
The module loads perfectly in the running kernel.

Trying to find a suitable vmblock module for your running kernel.

None of the pre-built vmblock modules for VMware Player is suitable for your
running kernel. Do you want this program to try to build the vmblock module
for your system (you need to have a C compiler installed on your system)?
[yes]

Extracting the sources of the vmblock module.

Building the vmblock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config4/vmblock-only'
make -C /usr/src/linux-headers-2.6.24-1-686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.24-1-686'
CC [M] /tmp/vmware-config4/vmblock-only/linux/block.o
CC [M] /tmp/vmware-config4/vmblock-only/linux/control.o
CC [M] /tmp/vmware-config4/vmblock-only/linux/dbllnklst.o
CC [M] /tmp/vmware-config4/vmblock-only/linux/dentry.o
CC [M] /tmp/vmware-config4/vmblock-only/linux/file.o
CC [M] /tmp/vmware-config4/vmblock-only/linux/filesystem.o
CC [M] /tmp/vmware-config4/vmblock-only/linux/inode.o
CC [M] /tmp/vmware-config4/vmblock-only/linux/module.o
CC [M] /tmp/vmware-config4/vmblock-only/linux/stubs.o
CC [M] /tmp/vmware-config4/vmblock-only/linux/super.o
LD [M] /tmp/vmware-config4/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config4/vmblock-only/vmblock.mod.o
LD [M] /tmp/vmware-config4/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-1-686'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-config4/vmblock-only'
The module loads perfectly in the running kernel.

Do you want networking for your virtual machines? (yes/no/help) [yes]

Configuring a bridged network for vmnet0.

Your computer has multiple ethernet network interfaces available: eth0, eth0:1.
Which one do you want to bridge to vmnet0? [eth0]

The following bridged networks have been defined:

. vmnet0 is bridged to eth0

Do you wish to configure another bridged network? (yes/no) [no]

Do you want to be able to use NAT networking in your virtual machines? (yes/no)
[yes]

Configuring a NAT network for vmnet8.

Do you want this program to probe for an unused private subnet? (yes/no/help)
[yes]

Probing for an unused private subnet (this can take some time)...

The subnet 172.16.220.0/255.255.255.0 appears to be unused.

The following NAT networks have been defined:

. vmnet8 is a NAT network on private subnet 172.16.220.0.

Do you wish to configure another NAT network? (yes/no) [no]

Do you want to be able to use host-only networking in your virtual machines?
[yes]

Configuring a host-only network for vmnet1.

Do you want this program to probe for an unused private subnet? (yes/no/help)
[yes]

Probing for an unused private subnet (this can take some time)...

The subnet 172.16.210.0/255.255.255.0 appears to be unused.

The following host-only networks have been defined:

. vmnet1 is a host-only network on private subnet 172.16.210.0.

Do you wish to configure another host-only network? (yes/no) [no]

Trying to find a suitable vmnet module for your running kernel.

None of the pre-built vmnet modules for VMware Player is suitable for your
running kernel. Do you want this program to try to build the vmnet module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vmnet module.

Building the vmnet module.

Unknown VMware Workstation 6.0.2 build 59824 detected. Building for Workstation 6.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config4/vmnet-only'
make -C /usr/src/linux-headers-2.6.24-1-686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.24-1-686'
CC [M] /tmp/vmware-config4/vmnet-only/driver.o
CC [M] /tmp/vmware-config4/vmnet-only/hub.o
CC [M] /tmp/vmware-config4/vmnet-only/userif.o
CC [M] /tmp/vmware-config4/vmnet-only/netif.o
CC [M] /tmp/vmware-config4/vmnet-only/bridge.o
CC [M] /tmp/vmware-config4/vmnet-only/filter.o
CC [M] /tmp/vmware-config4/vmnet-only/procfs.o
CC [M] /tmp/vmware-config4/vmnet-only/smac_compat.o
CC [M] /tmp/vmware-config4/vmnet-only/smac_linux.x386.o
LD [M] /tmp/vmware-config4/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config4/vmnet-only/vmnet.mod.o
LD [M] /tmp/vmware-config4/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-1-686'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config4/vmnet-only'
The module loads perfectly in the running kernel.

Starting VMware services:
Virtual machine monitor done
Blocking file system: done
Virtual ethernet done
Bridged networking on /dev/vmnet0 done
Host network detection done
Host-only networking on /dev/vmnet1 (background) done
DHCP server on /dev/vmnet1 done
Host-only networking on /dev/vmnet8 (background) done
DHCP server on /dev/vmnet8 done
NAT service on /dev/vmnet8 done

The configuration of VMware Player 2.0.2 build-59824 for Linux for this running
kernel completed successfully.

You can now run VMware Player by invoking the following command:
"/usr/bin/vmplayer".

Enjoy,

--the VMware team


-----------------------------------------------------------------------------

Ошибки, которые удалось обойти:
error: #error only bitops.h> can be included directly (решается пунктом 3)
gcc-4.1: error trying to exec 'cc1plus': execvp: (решается установкой g++-4.1)


Ну, а далее уже сюда: http://inf.by/linux/114/?phrase=vmware