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.
A lively discussion in the NANOG mailing list just recently ended with the disconnection of Intercage/Atrivo hosting company. This hosting company has been known to host customers with varying ethical standards.
One of the fallouts of this disconnection is that many malware websites are no longer reachable. This means if your computer has been compromised in the past, it may not be able to find its controller anymore. Sometimes, this means your computer won't work at all anymore.
Whenever there is a new kernel that comes out for Fedora, it is a treat to try and get VMware-server working again. For some reason the vmware modules need to be patched before they will compile.
For this last batch, I found that I had to upgrade to VMware-server-1.0.7 and apply the vmware-any-any-update117-itpsycho patch. Typically a vmware-any-any patch has solved these types of problems in the past, however, this one was tough to find. Here are the two articles that I finally found that put me on the correct path.