I'm having trouble with GSX Server on RHEL4(Nahant Beta 2). When I originally installed it, it said it could not find kernel module that was suitable for my kernel, so it would compile one. I haven't messed with the kernel in RHEL, and uname -r says the kernel is 2.6.9-1.648_EL. When it gets done compiling and stuff, it says the module loads perfectly into the kernel. So, OK. I restarted the vmware daemon in via /etc/init.d/vmware and it gives me an error message like this:
\----
Stopping VMware services:
Virtual machine monitor \[ OK ]
Bridged networking on /dev/vmnet0 \[ OK ]
Virtual ethernet \[ OK ]
VMware GSX Server is installed, but it has not been (correctly) configured
for the running kernel. To (re-)configure it, invoke the
following command: /usr/bin/vmware-config.pl.
\----
I had already run the vmware-config.pl during the install. I have lsmod'ed and grepped for anything with vm in it, but nothing shows up. I've also modprobe'd vmnet and vmmon, which looked to be the kernel modules that it was compiling.
I have tried running the vmware-config again, and here is the output from one of those attempts:
\----
aking sure services for VMware GSX Server are stopped.
Stopping VMware services:
Virtual machine monitor \[ OK ]
Bridged networking on /dev/vmnet0 \[ OK ]
Virtual ethernet \[ OK ]
Trying to find a suitable vmmon module for your running kernel.
None of the pre-built vmmon modules for VMware GSX 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.9-1.648_EL/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.9-1.648_EL/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/lib/modules/2.6.9-1.648_EL/build'
CC /tmp/vmware-config0/vmmon-only/linux/driver.o
CC /tmp/vmware-config0/vmmon-only/linux/hostif.o
CC /tmp/vmware-config0/vmmon-only/common/cpuid.o
CC /tmp/vmware-config0/vmmon-only/common/memtrack.o
CC /tmp/vmware-config0/vmmon-only/common/phystrack.o
CC /tmp/vmware-config0/vmmon-only/common/task.o
CC /tmp/vmware-config0/vmmon-only/common/vmx86.o
LD /tmp/vmware-config0/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST
CC /tmp/vmware-config0/vmmon-only/vmmon.mod.o
LD /tmp/vmware-config0/vmmon-only/vmmon.ko
make[1]: Leaving directory `/lib/modules/2.6.9-1.648_EL/build'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
The module loads perfectly in the running kernel.
This program previously created the file /dev/vmmon, and was about to remove it.
Somebody else apparently did it already.
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.9-1.648_EL/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/lib/modules/2.6.9-1.648_EL/build'
CC /tmp/vmware-config0/vmnet-only/driver.o
CC /tmp/vmware-config0/vmnet-only/hub.o
CC /tmp/vmware-config0/vmnet-only/userif.o
CC /tmp/vmware-config0/vmnet-only/netif.o
CC /tmp/vmware-config0/vmnet-only/bridge.o
CC /tmp/vmware-config0/vmnet-only/procfs.o
LD /tmp/vmware-config0/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST
CC /tmp/vmware-config0/vmnet-only/vmnet.mod.o
LD /tmp/vmware-config0/vmnet-only/vmnet.ko
make[1]: Leaving directory `/lib/modules/2.6.9-1.648_EL/build'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config0/vmnet-only'
The module loads perfectly in the running kernel.
You have already setup networking.
Would you like to skip networking setup and keep your old settings as they are?
(yes/no) \[yes]
Please specify a port for remote console connections to use \[903]
WARNING: VMware GSX Server has been configured to run on a port different from
the default port. Please make sure to use this port when installing remote
clients on other machines.
Stopping xinetd: \[ OK ]
Starting xinetd: \[ OK ]
Configuring the VMware VmPerl Scripting API.
Building the VMware VmPerl Scripting API.
Using compiler "/usr/bin/gcc". Use environment variable CC to override.
Installing the VMware VmPerl Scripting API.
The installation of the VMware VmPerl Scripting API succeeded.
Do you want this program to set up permissions for your registered virtual
machines? This will be done by setting new permissions on all files found in
the "/etc/vmware/vm-list" file. \[no]
Generating SSL Server Certificate
In which directory do you want to keep your virtual machine files?
/var/lib/vmware/Virtual Machines
Do you want to enter a serial number now? (yes/no/help) \[no]
Starting VMware services:
Virtual machine monitor \[ OK ]
Virtual ethernet \[ OK ]
Bridged networking on /dev/vmnet0 \[ OK ]
Starting VMware virtual machines... \[ OK ]
The configuration of VMware GSX Server 3.1.0 build-9089 for Linux for this
running kernel completed successfully.
\----
Oddly, one its done configuring that, it will work - until I restart the service or change runlevels. Does anyone know what the problem could be?