VMWare 4.5.2-8848 problem with new kernel 2.6.11-1.14_FC3

[David Gardner <thorjansen@xxxxxxxxxxxxx>]

After upgrading my system tonight with yum, I rebooted with the newest 
kernel (2.6.11-1.14_FC3). The system came up fine and everything appears 
to run normally, except for recompiling modules for VMWare 4.5.2-8848. 
First, I got an error that the kernel was built with gcc 3.4.3. As far 
as I can determine, that version hasn't been released yet for FC3 users 
under normal upgrade channels. After force compiling, I got an error 
trying to build a vmnet module (vmmon built okay, though). This has not 
happened in prior kernels, so something's changed significantly enough 
to break VMWare for the latest released kernel. I suspect it's gcc 
that's the culprit, with some significant header file changes that 
aren't out in the real world yet.

Here's the output of the build error:

~> vmware-config.pl

[output truncated for brevity]

Your kernel was built with "gcc" version "3.4.3", while you are trying 
to use
"/usr/bin/gcc" version "3.4.2". This configuration is not recommended and
VMwareWorkstation may crash if you'll continue. Please try to use exactly
same compiler as one used for building your kernel. Do you want to go with
compiler "/usr/bin/gcc" version "3.4.2" anyway? [no] yes

[output truncated for brevity]

Extracting the sources of the vmnet module.

Building the vmnet module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmnet-only'
make -C /lib/modules/2.6.11-1.14_FC3/build/include/.. SUBDIRS=$PWD 
SRCROOT=$PWD/. modules
make[1]: Entering directory `/lib/modules/2.6.11-1.14_FC3/build'
 CC [M]  /tmp/vmware-config1/vmnet-only/driver.o
 CC [M]  /tmp/vmware-config1/vmnet-only/hub.o
 CC [M]  /tmp/vmware-config1/vmnet-only/userif.o
In file included from /tmp/vmware-config1/vmnet-only/userif.c:45:
/tmp/vmware-config1/vmnet-only/pgtbl.h: In function `PgtblVa2PTELocked':
/tmp/vmware-config1/vmnet-only/pgtbl.h:81: warning: passing arg 1 of 
`pmd_offset' from incompatible pointer type
/tmp/vmware-config1/vmnet-only/userif.c: In function 
`VNetCopyDatagramToUser':
/tmp/vmware-config1/vmnet-only/userif.c:563: warning: implicit 
declaration of function `skb_copy_datagram'
 CC [M]  /tmp/vmware-config1/vmnet-only/netif.o
 CC [M]  /tmp/vmware-config1/vmnet-only/bridge.o
 CC [M]  /tmp/vmware-config1/vmnet-only/procfs.o
 LD [M]  /tmp/vmware-config1/vmnet-only/vmnet.o
 Building modules, stage 2.
 MODPOST
Warning: could not open /tmp/vmware-config1/vmnet-only/includeCheck.h: 
Success
*** Warning: "skb_copy_datagram" 
[/tmp/vmware-config1/vmnet-only/vmnet.ko] undefined!
 CC      /tmp/vmware-config1/vmnet-only/vmnet.mod.o
 LD [M]  /tmp/vmware-config1/vmnet-only/vmnet.ko
make[1]: Leaving directory `/lib/modules/2.6.11-1.14_FC3/build'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config1/vmnet-only'
Unable to make a vmnet module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config1/vmnet.o': -1 Unknown symbol 
in module
There is probably a slight difference in the kernel configuration 
between the
set of C header files you specified and your running kernel.  You may 
want to
rebuild a kernel based on that directory, or specify another directory.

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.