25 Oct
2007
25 Oct
'07
3:52 p.m.
On 10/22/07, Steve Berg sberg@mississippi.com wrote:
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.
Thanks, Steve; this turned out to be the problem!