[CentOS-virt] Fwd: 2 problems running CentOS 5.1 + kernel-vm in VMware Fusion

Fri Mar 7 19:44:49 UTC 2008
Leonardo Vilela Pinheiro <leonardo.pinheiro at dobemsoftware.com>

Hi,

Inside VMware Fusion 1.1.1, I have a virtual machine running CentOS
5.1 x86_64 with:
- kernel-vm-2.6.18-53.1.13.el5.x86_64.rpm from
http://people.centos.org/~tru/kernel-vm/5/RPMS/x86_64/
- kmod-open-vm-tools-0-0.20080123.2.6.18_53.1.13.el5vm.x86_64.rpm from
http://people.centos.org/~hughesjr/open-vm-tools/5/x86_64/

First problem:

Sometimes (most times) I get this error during boot (first error):

"The VMware Tools poweron script did not run successfully in this
virtual machine - If you have configured a custom poweron script in
this virtual machine, please inspect it for errors; otherwise, please
submit a support request."

A screenshot of this error can be seen in:
http://www.scribd.com/doc/2228546/VMware-Fusion-error-running-CentOS-51-kernelvm

This problem is very strange, it doesn't happen on every boot, and
usually when I boot another kernel (like change kernel-vm to
"kernel-default" or back) it disappears and only appears again after
some reboots using the kernel-vm.

I don't know a safe path to reproduce this bug, and I also don't know
for sure if it only happens with kernel-vm.

Second problem:

When I try to suspend the virtual machine (clicking on "Suspend
Guest"), I get the error that can be seen in:
http://www.scribd.com/doc/2232883/VMware-Fusion-running-CentOS-51-kernelvm-doesnt-Suspend

When I try to suspend again, it gives no error and suspends, but when
it resumes it gives the error that can be seen in:
http://www.scribd.com/doc/2233720/CentOS-51-in-VMware-Fusion-resuming-from-suspend

The second problem also happens when using:
- kernel-2.6.18-53.1.14.el5 (default kernel)
- kmod-open-vm-tools-0-0.20080123.2.6.18_53.1.13.el5vm.x86_64.rpm

The second problem does *not* happen when using:
- kernel-2.6.18-53.1.14.el5 (default kernel) or
kernel-vm-2.6.18-53.1.13.el5.x86_64.rpm
- default vmware-tools (which comes with VMware Fusion 1.1.1).

So it might be a problem in kmod-open-vm-tools.

If I may help debugging something, please tell me what to show you.

--
Leonardo