What crashed? Terminal emulator? Then you should ask Fedora...

If you just got some other error, I would recommend downloading and applying vmware-any-any-update101. You are trying to use system which was released long after Workstation version you are using, and this requires some additional patches. Or you can use one of supported hosts, instead.

Yes, the terminal emulator crashed to the desk top.
Hence, I can not even say what line of the script casued the crash.
However, out of desperation (and an old habit of hacking), I applied the any any patch.
The result was rather interesting as posted below:
**************************-
Updating /usr/bin/vmware-config.pl ... now patched
Updating /usr/bin/vmware ... No patch needed/available
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] y

Making sure services for VMware Workstation are stopped.

Stopping VMware services:
Virtual machine monitor [ OK ]

Configuring fallback GTK+ 2.4 libraries.

In which directory do you want to install the mime type 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 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)? [yes] y

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/kernels/2.6.16-1.2080_FC5-i686/include]

Extracting the sources of the vmmon module.

Building the vmmon module.

Building for VMware Workstation 5.5.x.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmmon-only'
make -C /usr/src/kernels/2.6.16-1.2080_FC5-i686/include/.. SUBDIRS=$PWD SRCROOT= $PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.16-1.2080_FC5-i686'
CC [M] /tmp/vmware-config1/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config1/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config1/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config1/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config1/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config1/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config1/vmmon-only/common/task.o
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for Ada/C/O bjC but not for C++
cc1plus: warning: command line option "-Wdeclaration-after-statement" is valid f or C/ObjC but not for C++
cc1plus: warning: command line option "-Wno-pointer-sign" is valid for C/ObjC bu t not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for Ada/C/O bjC but not for C++
cc1plus: warning: command line option "-ffreestanding" is valid for C/ObjC but n ot for C++
/tmp/vmware-config1/vmmon-only/common/task_compat.h: In function ‘void Task_Swit ch_V45(VMDriver*, Vcpuid)’:
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterStat e$validEIP’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterStat e$cs’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterStat e$rsp’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterStat e$rip’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunV M_V4(VMDriver*, Vcpuid) [with VMCrossPage = VMCrossPageV4]’:
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$validEIP’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$cs’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$rsp’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$rip’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunV M(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV321]’:
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1522: warning: ‘sysenterStat e$rsp’ is used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1523: warning: ‘sysenterStat e$rip’ is used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$validEIP’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$cs’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunV M(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageGSX1]’:
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1522: warning: ‘sysenterStat e$rsp’ is used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1523: warning: ‘sysenterStat e$rip’ is used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$validEIP’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$cs’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunV M(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV3]’:
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1522: warning: ‘sysenterStat e$rsp’ is used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1523: warning: ‘sysenterStat e$rip’ is used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$validEIP’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$cs’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunV M(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV2]’:
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1522: warning: ‘sysenterStat e$rsp’ is used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1523: warning: ‘sysenterStat e$rip’ is used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$validEIP’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$cs’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunV M(VMDriver*, Vcpuid)’:
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1522: warning: ‘sysenterStat e$rsp’ is used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1523: warning: ‘sysenterStat e$rip’ is used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$validEIP’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$cs’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$validEIP’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$cs’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$rsp’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$rip’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$validEIP’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$cs’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$rsp’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterStat e$rip’ may be used uninitialized in this function
CC [M] /tmp/vmware-config1/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config1/vmmon-only/vmcore/compat.o
CC [M] /tmp/vmware-config1/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config1/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST
CC /tmp/vmware-config1/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config1/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.16-1.2080_FC5-i686'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config1/vmmon-only'
The module loads perfectly in the running kernel.
******************************************---

Now, even with all these compile errors I tried to launch vmware. And it does launch.
I tried to install win 98. As win98 reboots, vmware reports there is a non bootable disk in the cd drive. Not true as it had started the win 98 install. I never did get win 98 installed.
Win XP did install with no problems, vmware tools also installed with no problems.
So, at the moment I do have a win XP machine I can try some applications on.
With all the vmware compile errors and not understanding the significance of them, I do expect it to be unstable.

Any info you can give me on the significance of the compile errors (and how to make them go away) is appreciated.
Many thanks,

Okay, lesson for the day -- Make is _VERY_ picky. I had inadvertently placed a space after the trailing line continuation marker (\). I removed the highly offensive space, and all is well. VMWare is properly configured, and launched.

petr,

I will give the win98 another try. Thanks for the suggestion.

any comment on all the compile warnings?

These changes helped me get vmware workstation 5 working on my computer which is:

AMD Turion 64 running FC5 for i386 with Linux 2.6.16-1.2096_FC5

Just wanted to say THANKS!!! to all of you for helping me out with this...

I made the changes to 2 lines in vmware-config.pl
I added 1 line to vmmon-only/Makefile.kernel
I added 1 line to vmnet-only/Makefile.kernel

and that took care of everything, I am up and running with VMWare Workstation 5 now

yay!

boo cain

I have installed 2.6.16-1.2096_FC4-i686 on my fedora 4 machine and get the same "kernel space issue". I applied the patch, but now get the following from the script at the module build, any suggestions???

***********************************************************
Building the vmmon module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmmon-only'
make -C /usr/src/kernels/2.6.16-1.2096_FC4-i686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.16-1.2096_FC4-i686'
CC [M] /tmp/vmware-config1/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config1/vmmon-only/linux/driver.h:20,
from /tmp/vmware-config1/vmmon-only/linux/driver.c:49:
/tmp/vmware-config1/vmmon-only/./include/compat_wait.h:37:5: warning: "VMW_HAVE_EPOLL" is not defined
/tmp/vmware-config1/vmmon-only/./include/compat_wait.h:43:5: warning: "VMW_HAVE_EPOLL" is not defined
In file included from /tmp/vmware-config1/vmmon-only/linux/driver.h:20,
from /tmp/vmware-config1/vmmon-only/linux/driver.c:49:
/tmp/vmware-config1/vmmon-only/./include/compat_wait.h:60: error: conflicting types for ‘poll_initwait’
include/linux/poll.h:45: error: previous declaration of ‘poll_initwait’ was here
/tmp/vmware-config1/vmmon-only/linux/driver.c:145: warning: initialization from incompatible pointer type
/tmp/vmware-config1/vmmon-only/linux/driver.c:149: warning: initialization from incompatible pointer type
make[2]: *** [/tmp/vmware-config1/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-config1/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.16-1.2096_FC4-i686'
make: *** [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.

O erro se refere a uma linha ( 1982 ) de comando dentro do arquivo : vmware-config.pl
na pasta /usr/bin

if ($header_page_offset =~ /[0-9a-fA-F]{8,}/) {
# We found a valid page offset
if (defined($gSystem{'page_offset'}) and
not (lc($header_page_offset) eq lc($gSystem{'page_offset'}))) {
if ($source eq 'user') {
print wrap('The kernel defined by this directory of header files does '
. 'not have the same address space size as your running '
. 'kernel.' . "\n\n", 0);
}
# return ''; ( coloque este # para comentar a linha e execute novamente o arquivo vmware-config.pl )
}
}