Hi.
I am using Debian with its kernel v2.6.22-1-k7 (#1 SMP Sun Jul 29 15:15:55 UTC 2007 i686). I had VMware v5.5.7 and upgraded to v5.5.8 (installed into /home/Programs/VMware558/ for doc, man, and lib), but I am having problems starting my VMware even after running vmware-any-any-update115.tar.gz and making modules successfully.
When I try to start my old Windows 2000 SP4 VMware v5.5.7 guest image, I get these three errors:
"Version mismatch with vmmon module: expecting 138.0, got 137.0. You have an incorrect version of the 'vmmon' kernel module. Try reinstalling VMware Workstation."
"Failed to initalize monitor device."
"Unable to change virtual machine power state: Cannot find a valid peer process to connect to."
Here is what I did:
$ cd /home/Programs/VMware558/
$ ls -l
total 1912
drwxr-xr-x 2 root staff 4096 2008-08-31 09:50 doc
drwxr-xr-x 17 root staff 4096 2008-08-31 09:50 lib
drwxr-xr-x 3 root staff 4096 2008-08-31 09:50 man
-r-xr-xr-x 1 root staff 6160 2008-08-31 09:50 vmnet-bridge
-r-xr-xr-x 1 root staff 110872 2008-08-31 09:50 vmnet-dhcpd
-r-xr-xr-x 1 root staff 118884 2008-08-31 09:50 vmnet-natd
-r-xr-xr-x 1 root staff 5192 2008-08-31 09:50 vmnet-netifup
-r-xr-xr-x 1 root staff 8140 2008-08-31 09:50 vmnet-sniffer
-r-xr-xr-x 1 root staff 4574 2008-08-31 09:50 vmplayer
-r-xr-xr-x 1 root staff 4946 2008-08-31 09:50 vmrun
-r-xr-xr-x 1 root staff 12292 2008-08-31 09:50 vm-support
-r-xr-xr-x 1 root staff 4570 2008-08-31 09:50 vmware
-r-xr-xr-x 1 root staff 287265 2008-08-31 09:50 vmware-config.pl
-r-xr-xr-x 1 root staff 490464 2008-08-31 09:50 vmware-loop
-r-xr-xr-x 1 root staff 25489 2008-08-31 09:50 vmware-mount.pl
-r-sr-xr-x 1 root staff 10852 2008-08-31 09:50 vmware-ping
-r-xr-xr-x 1 root staff 95436 2008-08-31 09:50 vmware-uninstall.pl
-r-xr-xr-x 1 root staff 695752 2008-08-31 09:50 vmware-vdiskmanager
I downloaded http://platan.vc.cvut.cz/ftp/pub/vmware/vmware-any-any-update115.tar.gz since I couldn't compile my VMware v5.5.8 modules.
$ tar -xzvf vmware-any-any-update115.tar.gz
vmware-any-any-update115/
vmware-any-any-update115/services.sh
vmware-any-any-update115/runme.pl
vmware-any-any-update115/update.c
vmware-any-any-update115/vmnet.tar
vmware-any-any-update115/update
vmware-any-any-update115/vmblock.tar
vmware-any-any-update115/vmmon.tar
$ cd vmware-any-any-update115
$ ls
runme.pl services.sh update update.c vmblock.tar vmmon.tar vmnet.tar
ls -l
total 2436
-rwxr-xr-x 1 ant ant 25263 2007-07-22 03:40 runme.pl
-rwxr-xr-x 1 ant ant 32159 2005-07-09 16:48 services.sh
-rwxr-xr-x 1 ant ant 21708 2006-02-19 00:51 update
-rw-rr 1 ant ant 27575 2006-02-19 00:51 update.c
-rrr-- 1 ant ant 307200 2007-11-28 02:37 vmblock.tar
-rw-rr 1 ant ant 1525760 2007-11-28 03:01 vmmon.tar
-rw-rr 1 ant ant 532480 2007-11-28 02:32 vmnet.tar
./runme.pl
Updating /home/Programs/VMware558/vmware-config.pl ... corrupted
Updating /home/Programs/VMware558/vmware ... No patch needed/available
Updating /home/Programs/VMware558/vmnet-bridge ... No patch needed/available
Updating /home/Programs/VMware558/lib/bin/vmware-vmx ... No patch needed/available
Updating /home/Programs/VMware558/lib/bin-debug/vmware-vmx ... No patch needed/available
VMware modules in "/home/Programs/VMware558/lib/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:
"/home/Programs/VMware558/vmware-config.pl". Do you want this script to invoke
Making sure services for VMware Workstation are stopped.
Stopping VMware services:
Virtual machine monitor done
Bridged networking on /dev/vmnet0 done
DHCP server on /dev/vmnet1 done
Host-only networking on /dev/vmnet1 done
DHCP server on /dev/vmnet8 done
NAT service on /dev/vmnet8 done
Host-only networking on /dev/vmnet8 done
Virtual ethernet done
Configuring fallback GTK+ 2.4 libraries.
In which directory do you want to install the mime type icons?
What directory contains your desktop menu entry files? These files have a
In which directory do you want to install the application's icon?
/usr/share/applications/vmware-workstation.desktop: warning: value "vmware-workstation.png" for key "Icon" in group "Desktop Entry" is an icon name with an extension, but there should be no extension as described in the Icon Theme Specification if the value is not an absolute path
/usr/share/applications/vmware-player.desktop: warning: value "vmware-player.png" for key "Icon" in group "Desktop Entry" is an icon name with an extension, but there should be no extension as described in the Icon Theme Specification if the value is not an absolute path
Trying to find a suitable vmmon module for your running kernel.
None of the pre-built vmmon modules for VMware Workstation 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)?
Using compiler "/usr/bin/gcc". Use environment variable CC to override.
Your kernel was built with "gcc" version "4.1.3", while you are trying to use
"/usr/bin/gcc" version "4.3.1". This configuration is not recommended and
VMware Workstation may crash if you'll continue. Please try to use exactly same
compiler as one used for building your kernel. Do you want to go with compiler
"/usr/bin/gcc" version "4.3.1" anyway? yes
What is the location of the directory of C header files that match your running
Extracting the sources of the vmmon module.
Building the vmmon module.
VMware 2 or VMware Express detected, building for VMware 2, VMware Express and VMware Workstation 4.0.x.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmmon-only'
make -C /lib/modules/2.6.22-1-k7/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.22-1-k7'
/tmp/vmware-config1/vmmon-only/Makefile:126: *** Inappropriate build environment: you wanted to use gcc version 4.3.1 while kernel attempts to use gcc version 4.1.3.
/tmp/vmware-config1/vmmon-only/Makefile:128: *** For proper build you'll have to replace gcc-4.1 -m32 with symbolic link to /usr/bin/gcc. Stop.
make[1]: Leaving directory `/usr/src/linux-headers-2.6.22-1-k7'
make: *** http://vmmon.ko Error 2
make: Leaving directory `/tmp/vmware-config1/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.
<< I made a symbolic link for gcc to use 4.1.3 instead of 4.3). >>
gcc --version
gcc (GCC) 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
ls
runme.pl services.sh update update.c vmblock.tar vmmon.tar vmnet.tar
./runme.pl
Updating /home/Programs/VMware558/vmware-config.pl ... corrupted
Updating /home/Programs/VMware558/vmware ... No patch needed/available
Updating /home/Programs/VMware558/vmnet-bridge ... No patch needed/available
Updating /home/Programs/VMware558/lib/bin/vmware-vmx ... No patch needed/available
Updating /home/Programs/VMware558/lib/bin-debug/vmware-vmx ... No patch needed/available
VMware modules in "/home/Programs/VMware558/lib/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:
"/home/Programs/VMware558/vmware-config.pl". Do you want this script to invoke
Making sure services for VMware Workstation are stopped.
Stopping VMware services:
Virtual machine monitor done
Bridged networking on /dev/vmnet0 done
DHCP server on /dev/vmnet1 done
Host-only networking on /dev/vmnet1 done
DHCP server on /dev/vmnet8 done
NAT service on /dev/vmnet8 done
Host-only networking on /dev/vmnet8 done
Virtual ethernet done
Configuring fallback GTK+ 2.4 libraries.
In which directory do you want to install the mime type icons?
What directory contains your desktop menu entry files? These files have a
In which directory do you want to install the application's icon?
/usr/share/applications/vmware-workstation.desktop: warning: value "vmware-workstation.png" for key "Icon" in group "Desktop Entry" is an icon name with an extension, but there should be no extension as described in the Icon Theme Specification if the value is not an absolute path
/usr/share/applications/vmware-player.desktop: warning: value "vmware-player.png" for key "Icon" in group "Desktop Entry" is an icon name with an extension, but there should be no extension as described in the Icon Theme Specification if the value is not an absolute path
Trying to find a suitable vmmon module for your running kernel.
None of the pre-built vmmon modules for VMware Workstation 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)?
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
Extracting the sources of the vmmon module.
Building the vmmon module.
VMware 2 or VMware Express detected, building for VMware 2, VMware Express and VMware Workstation 4.0.x.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config2/vmmon-only'
make -C /lib/modules/2.6.22-1-k7/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.22-1-k7'
CC /tmp/vmware-config2/vmmon-only/linux/driver.o
CC /tmp/vmware-config2/vmmon-only/linux/driverLog.o
CC /tmp/vmware-config2/vmmon-only/linux/hostif.o
CC /tmp/vmware-config2/vmmon-only/common/comport.o
CC /tmp/vmware-config2/vmmon-only/common/cpuid.o
CC /tmp/vmware-config2/vmmon-only/common/hash.o
CC /tmp/vmware-config2/vmmon-only/common/memtrack.o
CC /tmp/vmware-config2/vmmon-only/common/phystrack.o
CC /tmp/vmware-config2/vmmon-only/common/task.o
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-config2/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCrossPage, VMDriver) ':
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2491: warning: ‘sysenterState.SysenterStateV45::rsp' is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2492: warning: ‘sysenterState.SysenterStateV45::rip' is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::validEIP' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::cs' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCrossPage, VMDriver) ':
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2491: warning: ‘sysenterState.SysenterStateV45::rsp' is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2492: warning: ‘sysenterState.SysenterStateV45::rip' is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::validEIP' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::cs' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCrossPage, VMDriver) ':
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2491: warning: ‘sysenterState.SysenterStateV45::rsp' is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2492: warning: ‘sysenterState.SysenterStateV45::rip' is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::validEIP' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::cs' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCrossPage, VMDriver) ':
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2491: warning: ‘sysenterState.SysenterStateV45::rsp' is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2492: warning: ‘sysenterState.SysenterStateV45::rip' is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::validEIP' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::cs' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM_V4(VMDriver*, Vcpuid) ':
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::validEIP' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::cs' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::rsp' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::rip' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMDriver*, Vcpuid)':
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2491: warning: ‘sysenterState.SysenterStateV45::rsp' is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2492: warning: ‘sysenterState.SysenterStateV45::rip' is used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::validEIP' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::cs' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::validEIP' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::cs' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::rsp' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::rip' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::validEIP' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::cs' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::rsp' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:3028: warning: ‘sysenterState.SysenterStateV45::rip' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h: In function ‘void Task_Switch_V45(VMDriver*, Vcpuid)':
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::validEIP' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::cs' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::rsp' may be used uninitialized in this function
/tmp/vmware-config2/vmmon-only/common/task_compat.h:2666: warning: ‘sysenterState.SysenterStateV45::rip' may be used uninitialized in this function
CC /tmp/vmware-config2/vmmon-only/common/vmciContext.o
CC /tmp/vmware-config2/vmmon-only/common/vmciDatagram.o
CC /tmp/vmware-config2/vmmon-only/common/vmciDriver.o
CC /tmp/vmware-config2/vmmon-only/common/vmciDs.o
CC /tmp/vmware-config2/vmmon-only/common/vmciGroup.o
CC /tmp/vmware-config2/vmmon-only/common/vmciHashtable.o
CC /tmp/vmware-config2/vmmon-only/common/vmciProcess.o
CC /tmp/vmware-config2/vmmon-only/common/vmciResource.o
CC /tmp/vmware-config2/vmmon-only/common/vmciSharedMem.o
CC /tmp/vmware-config2/vmmon-only/common/vmx86.o
CC /tmp/vmware-config2/vmmon-only/vmcore/compat.o
CC /tmp/vmware-config2/vmmon-only/vmcore/moduleloop.o
LD /tmp/vmware-config2/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config2/vmmon-only/vmmon.mod.o
LD /tmp/vmware-config2/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.22-1-k7'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config2/vmmon-only'
The module loads perfectly in the running kernel.
You have already setup networking.
Would you like to skip networking setup and keep your old settings as they are?
Extracting the sources of the vmnet module.
Building the vmnet module.
VMware 2 or VMware Express detected, building for VMware 2, VMware Express and VMware Workstation 4.0.x.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config2/vmnet-only'
make -C /lib/modules/2.6.22-1-k7/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.22-1-k7'
CC /tmp/vmware-config2/vmnet-only/driver.o
CC /tmp/vmware-config2/vmnet-only/hub.o
CC /tmp/vmware-config2/vmnet-only/userif.o
CC /tmp/vmware-config2/vmnet-only/netif.o
CC /tmp/vmware-config2/vmnet-only/bridge.o
CC /tmp/vmware-config2/vmnet-only/filter.o
CC /tmp/vmware-config2/vmnet-only/procfs.o
CC /tmp/vmware-config2/vmnet-only/smac_compat.o
CC /tmp/vmware-config2/vmnet-only/smac_linux.x386.o
LD /tmp/vmware-config2/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config2/vmnet-only/vmnet.mod.o
LD /tmp/vmware-config2/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.22-1-k7'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config2/vmnet-only'
The module loads perfectly in the running kernel.
Starting VMware services:
Virtual machine monitor done
Virtual ethernet done
Bridged networking on /dev/vmnet0 done
Host-only networking on /dev/vmnet1 (background) done
Host-only networking on /dev/vmnet8 (background) done
NAT service on /dev/vmnet8 done
The configuration of VMware Workstation 5.5.8 build-108000 for Linux for this
running kernel completed successfully.
You can now run VMware Workstation by invoking the following command:
"/home/Programs/VMware558/vmware".
Enjoy,
--the VMware team
What's wrong and how do I fix this? Thank you in advance.
I wonder if downgrading back to v5.5.7 will work even though it has security holes according to http://www.vmware.com/support/ws55/doc/releasenotes_ws55.html#bugfix558 ... So far, no other replies.
I wonder if downgrading back to v5.5.7 will work
Just try
it has security holes according to
For my whole life I haven't seen any real in-the-wild malware targeting specifically VM or VM guest, so I can reassure you that you are pretty safe running even old VMWare versions.
I wonder if downgrading back to v5.5.7 will work
Just try
it has security holes according to
For my whole life I haven't seen any real in-the-wild malware targeting specifically VM or VM guest, so I can reassure you that you are pretty safe running even old VMWare versions.
I will. Heh, I still have v3.2.0 and v4.5.1(?) on my other machines at work! I am just lazy to upgrade the guest images.
I wonder if downgrading back to v5.5.7 will work
Just try
Nope. Same problem. I also tried running VMware as root (su), but same problem.
Message was edited by: ant
FYI from a log in /tmp/vmware-ant/ (use http://pastie.org/271044 for a clean format since the forum likes to change things):
Sep 11 23:14:57: vmx| Log for VMware Workstation pid=14413 version=5.5.8 build=build-108000 option=Release
Sep 11 23:14:57: vmx| Command line: "/home/Programs/VMware558/lib/vmware/bin/vmware-vmx" "-@" "pipe=/tmp/vmware-ant/vmxd2f75f23b0e67a82;vm=d2f75f23b0e67a82" "/extra/vmware/test/Windows 2000 Professional.vmx"
Sep 11 23:14:57: vmx| UI Connecting to pipe '/tmp/vmware-ant/vmxd2f75f23b0e67a82' with user '(null)'
Sep 11 23:14:57: vmx| Using system libcrypto, version 9070DF
Sep 11 23:14:57: vmx| Msg_Post: Error
Sep 11 23:14:57: vmx| http://msg.vmmonPosix.badVersion Version mismatch with vmmon module: expecting 138.0, got 168.0.
Sep 11 23:14:57: vmx| http://msg.vmmonPosix.badDriver You have an incorrect version of the `vmmon' kernel module.
Sep 11 23:14:57: vmx| Try reinstalling VMware Workstation.
Sep 11 23:14:57: vmx| -
Sep 11 23:14:59: vmx| Msg_Post: Error
Sep 11 23:14:59: vmx| http://msg.vmmonPosix.initFailed Failed to initialize monitor device.
Sep 11 23:14:59: vmx| -
Sep 11 23:14:59: vmx| Module VMMon initialization failed.
Sep 11 23:14:59: vmx| Flushing VMX VMDB connections
Sep 11 23:14:59: vmx| Failed to initialize VM.
You are still trying to run VMWare 5.x.x with VMWare 6.0 kernel modules. As we both know it won't work for you. I suggest waiting for an answer from the google vmware group.
And if you are a paying customer, why don't you just ask VMWare's support team directly? Most people on this forum either run VMWare 5.x with older kernels or have already upgraded to ... VMWare 6.5RC1 - it's quite stable.
You are still trying to run VMWare 5.x.x with VMWare 6.0 kernel modules. As we both know it won't work for you. I suggest waiting for an answer from the
google vmware group.
Are you saying that VMware-any-any patch is only for v6.0? If so, then where are the older ones with v5?
And if you are a paying customer, why don't you just ask VMWare's support team directly? Most people on this forum either run VMWare 5.x with older kernels or have already upgraded to ... VMWare 6.5RC1 - it's quite stable.
According to http://store.vmware.com/servlet/ControllerServlet?Action=DisplayPage&Env=BASE&Locale=en_US&SiteID=vm... ... I will have to pay for support. I have had VMware v5.0 (since its first release) for three years or so. I already exceeded the first 30 days of free trial and over a year after its purchase. Am I missing something?
I wished v6 was free for v5 so I avoid paying. v5 was expensive enough.
I got a minor Kernel upgrade from Debian today: 2.6.26-1-686 #1 SMP Wed Sep 10 16:46:13 UTC 2008 i686 GNU/Linux, rebooted, and retried with VMware. Same results.
I discovered VirtualBox and loved it. And it's free! I am going to dump VMware since it is not working out.
I noticed someone else has similiar problems in my http://groups.google.com/group/vmkernelnewbies/tree/browse_frm/thread/a440c0e70351af6b/f77c9702df23b...ORphilpi%40earthlink.netANTORphillip_pi%40symantec.comSYMCORantdude%40gmail.comORant%40zimage.comORphilpi%40earthlink.net&_done=%2Fgroup%2Fvmkernelnewbies%2Fbrowse_frm%2Fthread%2Fa440c0e70351af6b%2Fe7d821aea86f2525%3Flnk%3Dst%26q%3Dantant%2540zimage.com%2BOR%2Bphilpi%2540earthlink.netANT%2BOR%2Bphillip_pi%2540symantec.comSYMC%2BOR%2Bantdude%2540gmail.com%2BOR%2Bant%2540zimage.com%2BOR%2Bphilpi%2540earthlink.net%26#doc_5147bd431fd88d0b newsgroup thread.
FYI:
From: VMware Technical Support
Sent: Thursday, September 18, 2008 2:05 PM
Subject: RE: VMware Support Request
Unfortunately, with your unsupported configuration, especially having to use third party "hacks", we can't delve into this issue deeply.
I did ask around with some of the Linux guys here and none had suggestions for you. Most commented that you're still running 5.5, although even if you were on WS6, Debian is still not an officially supported platform.
You may be interested in trying the WS6.5 beta to see if that helps, but again, a base install using Debian is not on the supported list.
http://www.vmware.com/communities/content/beta/ws65/welcome.html
Please see the documentation on the download page for the manual which lists the supported platforms and guests.
Mike S.
Technical Support Engineer
VMware Global Support Services