-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Install and config of VMware 3.2 is proving to be a nightmare. I found this on Google:
VMware has a problem with Suse 8.0.
Suse decided to include a memory management patch from the 2.5.x kernel tree in their 2.4.x kernels. Applications that are not specifically modified for this patch can be severely broken by it.
VMware was not written to take this patch into account because VMware only supports 2.2.x and 2.4.x kernels on the host and this patch is *NOT* part of the 2.2.x or 2.4.x kernels.
Suse should not be claiming that the kernel shipped with Suse 8.0 is a 2.4.18 kernel. It is not. It is a heavily modified kernel that was originally based on 2.4.18. VMware is compatible with 2.4.18 kernels. It is not 100% compatible with the custom kernel installed by default in Suse 8.0 (please note that Suse 8.0 is not a supported host OS)
Replacing your patched Suse kernel with a stock 2.4.18 kernel will resolve the problem completely.
a fast an simple solution is to limit RAM to 850 MB at bootime, works but if you need the RAM....
Whether you need the RAM or not, the better solution is to remove that patch. Apparently even the author of the patch has said that the only people who should see any benefit from it right now are people with more than 1GB of RAM, but less than 2GB of RAM who are also running Oracle on the machine. So removing it should not hurt anything.
So is the only fix to use kernel.org kernels? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj2XoIIACgkQnQ18+PFcZJtREQCfXcbD8Bfueuky9/0dAe6vH8NX 55cAniZA0uVO5sDKf0La3twX02wKv+Q+ =aqb7 -----END PGP SIGNATURE-----