CentOS - Sep 2008 - VMWare Server doesn't like new CentOS installation?

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

Am 04.09.2008 um 03:22 schrieb MHR:
> 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.

It's not officially supported.
I think 4.4 is the last supported version.
Install Server 2.0 or try the new ESXi directly...



Rainer

MHR wrote:
<smip>
> 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:
<snip>

I upgraded to 1.0.7 from 6 without issue.  Since your machine is brand 
new, my first thought was you may not have installed the appropriate 
rpms, kernel* comes to mind.

CentOS52[root at beast ~]# rpm -qa | grep -i vmware
xorg-x11-drv-vmware-10.13.0-2.1
VMware-server-1.0.7-108231

CentOS52[root at beast ~]# rpm -qa | grep -i 2.6.18-92.1.10
kernel-devel-2.6.18-92.1.10.el5.centos.plus
kernel-headers-2.6.18-92.1.10.el5.centos.plus
kernel-2.6.18-92.1.10.el5.centos.plus

I wonder if this is better for the virt list:
http://lists.centos.org/mailman/listinfo/centos-virt

-- 
Sincerely,
John Thomas

MHR wrote:
> 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).
Not sure what the issue is, it seems that vmware doesn't
detect the existence of xinetd on your system, in which case
just put in the config by hand

aphro at vmware2:/etc/xinetd.d$ cat vmware-authd
# default: on
# description: The VMware remote access authentification daemon
service vmware-authd
{
    disable         = no
    port            = 902
    socket_type     = stream
    protocol        = tcp
    wait            = no
    user            = root
    server          = /usr/sbin/vmware-authd
    type            = unlisted
}

And restart xinetd and off you go (if port 902 is in use then
use another).

The driver compilation looked like it worked fine(the message
said it loaded perfectly into the running kernel).

I'm not sure what sort of check vmware does for xinetd, but
the error is harmless, not an indication of a compatibility
issue with the distribution.

nate

On Wed, Sep 03, 2008 at 06:22:19PM -0700, MHR wrote:
> I just got a nice, shiny new machine at work, a Core 2 Duo, on which 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.
...
> 
> 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.
You don't have xinetd installed (not installed by default).
rpm -q xinetd || yum install xinetd
and re-run vmware-config.pl

btw, if you have SElinux enforced you will probably need to run:
restorecon -v /etc/services

Cheers,

Tru
-- 
Tru Huynh (mirrors, CentOS-3 i386/x86_64 Package Maintenance)
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://lists.centos.org/pipermail/centos/attachments/20080904/d01c3a53/attachment-0002.sig>

On Wed, Sep 3, 2008 at 11:53 PM, Tru Huynh <tru at centos.org>
wrote:
>
> You don't have xinetd installed (not installed by default).
> rpm -q xinetd || yum install xinetd
> and re-run vmware-config.pl
>
This is weird - I swear I checked that, and xinetd _was_ installed,
but I just checked again and, surprise, it was not.  Thanks!
> btw, if you have SElinux enforced you will probably need to run:
> restorecon -v /etc/services
>
I don't use selinux - don't like it.

mhr