CentOS - Oct 2007 - VMware not correctly configured for running kernel

Something happened over the weekend power-related on my VMware test
server, and when I came back and restarted my VMware server box
(running CentOS), I got the following message:

"VMware 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 ran that .pl script, answered all the questions (just entering in
the default values), and all seems to work ok now.

Is this someting VMware related?  CentOS 4 related?  Or possibly some
misconfiguration on my part? This box has been working fine for months
(and has been rebooted many times), so I'm not sure what "changed"
(certainly nothing on the host OS level).

Any help pointing me in the right direction would be greatly appreciated.

> Is this someting VMware related?  CentOS 4 related?  Or possibly some
> misconfiguration on my part? This box has been working fine for months
> (and has been rebooted many times), so I'm not sure what
"changed"
> (certainly nothing on the host OS level).
VMWare does this whenever you get a new kernel running.  It has to have a
module that matches so anytime you update the kernel, you have re-run the
config script to get a matching module compiled.
-- 
*       Stephen Berg       *
*  sberg at mississippi.com   *
* http://iceberg.3c0x1.com *
*  Sinners can repent,     *
*  But stupid is forever.  *

on 10/22/2007 11:28 AM Rogelio spake the following:
> Something happened over the weekend power-related on my VMware test
> server, and when I came back and restarted my VMware server box
> (running CentOS), I got the following message:
> 
> "VMware 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 ran that .pl script, answered all the questions (just entering in
> the default values), and all seems to work ok now.
> 
> Is this someting VMware related?  CentOS 4 related?  Or possibly some
> misconfiguration on my part? This box has been working fine for months
> (and has been rebooted many times), so I'm not sure what
"changed"
> (certainly nothing on the host OS level).
> 
> Any help pointing me in the right direction would be greatly appreciated.
Have you re-booted since the last kernel update?
Somewhere near the end of September.

-- 
MailScanner is like deodorant...
You hope everybody uses it, and
you notice quickly if they don't!!!!