Running VMware Server in FC6
I run VMware Server 1.0.1 for a number of different development tasks. At some point after upgrading Fedora, I used vmware-config.pl to reconfigure VMware for my new kernel. This basically means recompiling a few VMware kernel modules. I ran into this error message that halted my progress:
At first glance, missing a kernel header file seems like a bad thing. It turns out to be a simple issue though. The use of linux/config.h has been deprecated. It remained as a placeholder for a while, but it has now been completely removed. Since VMware has not been getting anything from that header, the fix is simple:
After that, vmware-config.pl completes successfully, and the world is right again. The only downer is that you have to do this extra step every time you upgrade the kernel. In all likelihood though, you would think VMware would address this issue in the next release.
/tmp/vmware-config4/vmnet-only/procfs.c:33:26: error: linux/config.h: No such file o directory
make[2]: *** [/tmp/vmware-config4/vmnet-only/procfs.o] Error 1
make[1]: *** [_module_/tmp/vmware-config4/vmnet-only] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.18-1.2868.fc6-i686'
make: *** [vmnet.ko] Error 2
make: Leaving directory `/tmp/vmware-config4/vmnet-only'
Unable to build the vmnet module.
At first glance, missing a kernel header file seems like a bad thing. It turns out to be a simple issue though. The use of linux/config.h has been deprecated. It remained as a placeholder for a while, but it has now been completely removed. Since VMware has not been getting anything from that header, the fix is simple:
touch /lib/modules/2.6.18-1.2868.fc6/build/include/linux/config.h
After that, vmware-config.pl completes successfully, and the world is right again. The only downer is that you have to do this extra step every time you upgrade the kernel. In all likelihood though, you would think VMware would address this issue in the next release.
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home