VMWARE 4.0 problems installing on Redhat 9

Pardon my ignorance, I'm a windows user.

I've been trying to install/configure VMWARE 4.0 on an install of Redhat 9. I'm stuck when the config asks "What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include]" . I've tried a few directories with no luck. I've also applied the vmware-any-any-update27 with no resulting change. Does version 4 even work with redhat 9 or am I more likely doing something wrong?

Please help.

I was not able to complete my install either

You have to have your kernel sources installed (not default). The Installer should be able to autodetect your sources after that.

Where do I get the Kernel sources so I can install them?

they are on the redhat cd´s. To install them just execute redhat-config-packages and mark the checkbox next to kernel-development.

Installed Kernel-development but still getting the same error:

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

The path "/usr/src/linux/include" is not an existing directory.

I checked on one of my boxes (also RH9) here it is /usr/src/linux-2.4/include
just for my curiosity I tried to install vmware: it works on my box with this directory
one thing you should keep in mind is that if you modify your kernel settings, for example if you want to compile your own customized kernel, you might get into trouble recompiling the vmware modules - that what happend to me with an older version of vmware - it took me a while to figure out what kernel settings vmware needs and wich are not allowed
if you would like to keep the default setting within the vmware installation then you also could make a symbolic link with the command
ln -s /usr/src/linux-2.4 /usr/src/linux

Thanks. Making some progress now. I also compiled a customized kernel to get here, but I'm getting a different error message that looks a little more optimistic.

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

The directory of kernel headers (version 2.4.20-9) does not match your running kernel (version 2.4.20-8). Even if the module were to compile successfully, it would not load into the running kernel.

Interesting! Did you really get the sources from the cd´s? It doesn´t look so. 2.4.20-9 is an errata kernel from redhat not the one wich was shipped with rh9. Anyhow - of course your kernel and the sources have to match. Otherwise you are compiling a module for a different kernel.

cheeselegacy:

It looks like you updated to the latest errata kernel without rebooting and starting it.

Reboot, start with -8 and give it a try.

After recompiling the kernel to get the C headers in the right path, there are now two options on teh boot loader. the new linux custom kernel didn't work, but failed with some initrd problem. The old option loaded up fine and VMWARE is WORKING with the 2.4.20-9 kernel. Thanks for all the help.

Now how do I clean up the mess I created by recompiling the kernel and remove the orphaned files I probably left behind.

Wow cool, how did you do it? I'm still trying...

I have 2.4.20-9 running, but I get a compile error.

It does complain about my version of gcc, but it allows me to continue past that.

It blows up on "warning: VNetProcessOwnsPort' defined but not used
make: *** [driver.o] Error 1
Unable to build the vmnet module

---Oh sweet I just got it running, the RPM didn't want to install for me but the tarball was fine.

Life is good again.

I'd tell you, but I don't understand linux well enough or what I really did to get it to work. Sorry.

Vmware is running now, but can't get XP installed. keep getting errors like "cannot execute binary file" and "Nautilus has no installed viewer capable of displaying "/mnt/cdrom/setup.exe"

I should have posted a new message instead of editing, but I did get it running.

The tarball seems to be more forgiving.

Robble,

Where you able to get an OS installed after you got VMWARE working? if you did, how did you do it? VMWARE start accessing the cdrom with "Setup is checking ...." then the drive spins down and stops.