You may faced the similar issue by default if you currently running your vcenter server 4 on top of Windows 2008. The reason of the services start up failure are due to the dependency setting require to add in manually.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007669
I found the KB above which describe in details about the root cause and solution to over come this.
This issue may occur if the VirtualCenter Server service starts before one of the services it depends on. The VirtualCenter Server service is dependent on the following services:
- SQL Services
- ADAM Services (when using linked mode in vCenter Server 4.0)
Read more »
I’m getting an “error message: 28038″ just before the VMware VCenter Server installation end as screen shot below:
Workaround:
Read more »
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1013013
You experience these symptoms:
Note: You are not affected if one of Service Console Port(s) or Management Network IP address(s) on your ESX host falls outside of this range.
vCenter 4.0 patch 1 will help to fix this issue.
Read more »
Most of us may had previously experienced a VM which hung in the ESX hosts. Usually we will use the command vmware-cmd utilities to kill or stop the virtual machine. Sometimes we even need to use the vm-support command to force the VM to be stop hardly if vmware-cmd was not worked. Today I found some interesting issue with 1 of the virtual machine. I had executed the instruction to power off from vCenter 4. This virtual machine is running on vsphere 4. After 2 minutes, the virtual machine still showed power on from the vCenter, and I executed again the 2nd command to power off, the system prompted that another process was in progress, and access was denied.
Read more »
I am currently doing some test to simulate the real update requirement for my production VMware Farm to be upgraded from ESX 3.5 to vSphere 4. To minimize the impact to our production system, we may want to do this with as minimal impact as possible. Due to the virtual hardware version and tools upgrade require, is pretty tough for us to perform the entire upgrade at 1 time. Therefore, our plan is get the host upgraded and follow by each individual virtual machine to be upgraded follow the suitable timing for different business unit. HA and DRS will need to be disable temp during the ESX upgrade.
I am able to get the ESX 3.5 to be manage by the latest vcenter. A vmotion from ESX 3.5 to vsphere 4 had been successes too, but the latest version of virtual machine which built from vSphere 4 might not compatible to vmotion back to the ESX 3.5 hosts. At the same time, if you have different processors chipset in the environment and require EVC to be turned on, it may be a little challenge to do so. You may want to ensure the EVC to be done with no down time. You may need to refer to my previous post about how to enable EVC with no down time.
Read more »
