[CentOS] VMWare Server doesn't like new CentOS installation?

MHR mhullrich at gmail.com
Thu Sep 4 01:22:19 UTC 2008


I just got a nice, shiny new machine at work, a Core 2 Duo, on which I
just finished installing CentOS 5.2 with a fair number of packages,
SeaMonkey 1.1.10, Adobe Reader 8.0, Adobe Flash 9.0, mplayer,
mplayerplug-in (both from rpmforge), and I think that was it.  Then I
went and got the latest VMWare Server, 1.0.7, from VMWare, pulled down
their rpm, installed it, and ran vmware-config.pl, which is what I
have to do (at home) after every new kernel install, too.

Except, this time it failed:

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.18-92.1.10.el5/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-92.1.10.el5-i686'
  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
  CC [M]  /tmp/vmware-config0/vmnet-only/procfs.o
  CC [M]  /tmp/vmware-config0/vmnet-only/smac_compat.o
  SHIPPED /tmp/vmware-config0/vmnet-only/smac_linux.x386.o
  LD [M]  /tmp/vmware-config0/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST
WARNING: could not find
/tmp/vmware-config0/vmnet-only/.smac_linux.x386.o.cmd for
/tmp/vmware-config0/vmnet-only/smac_linux.x386.o
  CC      /tmp/vmware-config0/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/vmware-config0/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.18-92.1.10.el5-i686'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config0/vmnet-only'
The module loads perfectly in the running kernel.

The default port : 902 is not free. We have selected a suitable alternative
port for VMware Server use. You may override this value now.
Remember to use this port when connecting to this server.
Please specify a port for remote console connections to use [904]

WARNING: VMware Server has been configured to run on a port different from the
default port. Remember to use this port when connecting to this server.
Unable to find any instance of the super-server "inetd" or "xinetd".  It is
possible that you do not have one of these packages installed on this machine.
Please install "inetd" or "xinetd".

If you do have "inetd" or "xinetd" installed, make sure that /etc/inetd.conf or
/etc/xinetd.d exists.
The configuration will continue, but you should re-run
/usr/bin/vmware-config.pl after you fix the super-server.

Hit enter to continue.

-----

I checked, and I am running xinetd, there _is_ an /etc/xinetd.d, and I
have no idea what is causing this.  I even went back, removed the
1.0.7 server and installed the 1.0.6 server, which I think is that
last one I installed at home, and that got the same error (actually,
the above is from the 1.0.6 install).

My new h/w: Intel Core 2 Duo E6750 2.66GHz, 2GB 667MHz DDR2 RAM, 160GB
hard drive, nvidia ge7300fs video card, not sure what mobo, but I
can't help but wonder if that has anything to do with it (does it???).
 Running CentOS 5.2 32-bit with all the latest updates.

Anyone know anything about this?  I asked in the VMWare forums, but
haven't got an answer yet (in fact, I rarely get answers there...).

Thanks.

mhr


More information about the CentOS mailing list