After Refreshing, VirtualCenter Reports Only the Memory Allocated to the Service Console and One CPU

The ccagent (which records hardware resources such as total memory information and the number of CPUs) can start before the VMkernel. This can happen if the xinetd service is started before the VMkernel. Once the xinetd service is up on the host, it starts up the authd, which in turn starts the ccagent. If ccagent starts before the VMkernel, you see incorrect reporting because the VMkernel is not available to provide accurate hardware information.

To prevent the xinetd service from running before the VMkernel, set the VMware init script run order to run the VMkernel before xinetd. To do this, manually change the script's run position, from 90 to 11.

To change the VMware init script's run order from 90 to 11, perform the following steps.

1. Update the run level information of the vmware service. Turn off run level 3 of the service using this command:

   chkconfig --level 3 vmware off

2. Go to /etc/init.d. Edit the vmware init script file. Change the line reading:

   # chkconfig: 3 90 08

   to:

   # chkconfig: 3 11 08

   All you have to do is change the number 90 to 11.

3. Save the change. This is read-only file. So you must force your text editor to write the file (for example, in vi, use the wq! command to save the file).
4. Update the run level information of the vmware service. Turn on run level 3 of the service using this command:

   chkconfig --level 3 vmware on

5. Go to the directory /etc/rc3.d. List all the files in this directory. You should see that vmware is now in the S11 position.

Your hardware resources should now be reported accurately.