VMware Server 1.06 on Fedora 8 x86_64

[Kam Leo]

2008/8/15 Gene Poole <gene.poole at macys.com>:
>
> Since we couldn't get past the text issues going from Linux to Windows, here
> is the complete and corrected message list when attempting to install VMware
> Server 1.06 onto a running Fedora 8 x86_64 machine:
>
>
> Configuring fallback GTK+ 2.4 libraries.
>
> In which directory do you want to install the mime type icons?
> [/usr/share/icons]
>
> What directory contains your desktop menu entry files? These files have a
> .desktop file extension. [/usr/share/applications]
>
> In which directory do you want to install the application's icon?
> [/usr/share/pixmaps]
>
> Trying to find a suitable vmmon module for your running kernel.
>
> None of the pre-built vmmon modules for VMware Server is suitable for your
> running kernel.  Do you want this program to try to build the vmmon module
> for
> your system (you need to have a C compiler installed on your system)? [yes]
>
> Using compiler "/usr/bin/gcc". Use environment variable CC to override.
>
> What is the location of the directory of C header files that match your
> running
> kernel? [/lib/modules/2.6.25.11-60.fc8/build/include]
>
> Extracting the sources of the vmmon module.
>
> Building the vmmon module.
>
> Using 2.6.x kernel build system.
> make: Entering directory `/tmp/vmware-config0/vmmon-only'
> make -C /lib/modules/2.6.25.11-60.fc8/build/include/.. SUBDIRS=$PWD
> SRCROOT=$PWD/. modules
> make[1]: Entering directory `/usr/src/kernels/2.6.25.11-60.fc8-x86_64'
>   CC [M]  /tmp/vmware-config0/vmmon-only/linux/driver.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/linux/hostif.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/comport.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/cpuid.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/hash.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/memtrack.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/phystrack.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/task.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciContext.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciDatagram.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciDriver.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciDs.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciGroup.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciHashtable.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciProcess.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciResource.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciSharedMem.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/vmx86.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.o
>   LD [M]  /tmp/vmware-config0/vmmon-only/vmmon.o
>   Building modules, stage 2.
>   MODPOST 1 modules
>   CC      /tmp/vmware-config0/vmmon-only/vmmon.mod.o
>   LD [M]  /tmp/vmware-config0/vmmon-only/vmmon.ko
> make[1]: Leaving directory `/usr/src/kernels/2.6.25.11-60.fc8-x86_64'
> cp -f vmmon.ko ./../vmmon.o
> make: Leaving directory `/tmp/vmware-config0/vmmon-only'
> The module loads perfectly in the running kernel.
>
> Do you want networking for your virtual machines? (yes/no/help) [yes]
>
> Configuring a bridged network for vmnet0.
>
> Your computer has multiple ethernet network interfaces available: eth0,
> eth1.
> Which one do you want to bridge to vmnet0? [eth0] eth1
>
> The following bridged networks have been defined:
>
> . vmnet0 is bridged to eth1
>
> Do you wish to configure another bridged network? (yes/no) [no]
>
> Do you want to be able to use NAT networking in your virtual machines?
> (yes/no) [yes]
>
> Configuring a NAT network for vmnet8.
>
> Do you want this program to probe for an unused private subnet?
> (yes/no/help) [yes]
>
> Probing for an unused private subnet (this can take some time)...
>
> The subnet 192.168.104.0/255.255.255.0 appears to be unused.
>
> The following NAT networks have been defined:
>
> . vmnet8 is a NAT network on private subnet 192.168.104.0.
>
> Do you wish to configure another NAT network? (yes/no) [no]
>
> Do you want to be able to use host-only networking in your virtual machines?
> [yes]
>
> Configuring a host-only network for vmnet1.
>
> Do you want this program to probe for an unused private subnet?
> (yes/no/help) [yes]
>
> Probing for an unused private subnet (this can take some time)...
>
> The subnet 172.16.15.0/255.255.255.0 appears to be unused.
>
> The following host-only networks have been defined:
>
> . vmnet1 is a host-only network on private subnet 172.16.15.0.
>
> Do you wish to configure another host-only network? (yes/no) [no]
>
> Extracting the sources of the vmnet module.
>
> Building the vmnet module.
>
> Using 2.6.x kernel build system.
> make: Entering directory `/tmp/vmware-config0/vmnet-only'
> make -C /lib/modules/2.6.25.11-60.fc8/build/include/.. SUBDIRS=$PWD
> SRCROOT=$PWD/. modules
> make[1]: Entering directory `/usr/src/kernels/2.6.25.11-60.fc8-x86_64'
>   CC [M]  /tmp/vmware-config0/vmnet-only/driver.o
>   CC [M]  /tmp/vmware-config0/vmnet-only/hub.o
>   CC [M]  /tmp/vmware-config0/vmnet-only/userif.o
>   CC [M]  /tmp/vmware-config0/vmnet-only/netif.o
>   CC [M]  /tmp/vmware-config0/vmnet-only/bridge.o
> /tmp/vmware-config0/vmnet-only/bridge.c: In function
> 'VNetBridgeDevCompatible':
> /tmp/vmware-config0/vmnet-only/bridge.c:278: error: implicit declaration of
> function dev_net'
> /tmp/vmware-config0/vmnet-only/bridge.c: In function 'VNetBridgeUp':
> /tmp/vmware-config0/vmnet-only/bridge.c:903: warning: passing argument 1 of
> '__dev_get_by_name' makes pointer from integer without a cast
> /tmp/vmware-config0/vmnet-only/bridge.c:941: warning: passing argument 1 of
> 'sk_alloc' makes pointer from integer without a cast
> make[2]: *** [/tmp/vmware-config0/vmnet-only/bridge.o] Error 1
> make[1]: *** [_module_/tmp/vmware-config0/vmnet-only] Error 2
> make[1]: Leaving directory `/usr/src/kernels/2.6.25.11-60.fc8-x86_64'
> make: *** [vmnet.ko] Error 2
> make: Leaving directory `/tmp/vmware-config0/vmnet-only'
> Unable to build the vmnet module.
>
> 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.
>
>
> If you notice the lines starting with 'Building the vmnet module.', this is
> where the failure starts.
>
> Thanks,
> Gene Poole

Have you installed the latest vmware-any-any-update patch?