Fedora updated the kernel to 18.104.22.168-45 over the weekend. I ran into many of the issues that I had before with getting VMware-server-1.0.7 working with the new kernel.
I was able to compile it using the same vmware-any-any-117-itpsycho patches, but it crashed the system whenever I tried to start a VM.
Toward the end of September, VMware released their VMware 2.0 product. I had tried a pre-release version, but it was not working well at that time. I decided to give the production version a try before reverting back to an older kernel.
Installing 2.0 went very easy. After registering online and downloading the RPM, I installed it with rpm -ivh.
After installation, I went through vmware-config.pl like normal. Here, it asked me for web ports as well. It appears that VMware-server-2.0 uses your web browser as the client. The default is to install a plain text web client on port 8222 and an SSL protected one on 8333. The "vmware" binary now launches your browser to the SSL url if available, otherwise to the non-SSL port.
The SSL port requires a user certificate. Under Firefox, this constantly brought up windows asking me to accept the use of this certificate. Once you try to login (using the username you specified during vmware-config.pl), the whole things hangs. I found this post claiming that there is an issue with pam authentication with vmware and suggests telling pam to allow no authentication. This is fine as long as you follow the iptables provisions that they speak of, and that you only allow trusted users on the system.
Afterwards, you don't need to type in a username. I found that the SSL version was unstable and didn't work that well. So, I switched to the non-SSL version. Being that the communication is on my local machine only, and I have the only account on it, I think that this was an ok choice. Your mileage may vary if you use VMware over the web.