VMware has become aware of an issue where:
- After upgrading to vCenter Server 5.1, the VMware VirtualCenter Server service fails to start
- The VMware VirtualCenter Server service will not successfully stop or start.
- The final log in the vpxd.log file shows:
CoreDump: Writing minidump
- You see a backtrace near the very bottom of the vpxd.log file which begins with the following:
2012-09-13T11:53:46.802+02:00 [04468 info 'vmmoVm' opID=SWI-c5103928] [VmMo::SetComputeCompatibilityDirty] vm vm-5345 is marked dirty
2012-09-13T11:53:46.786+02:00 [05112 warning 'win32vpxdOsLayer_win32' opID=SWI-56f04b9c] [VpxUnhandledException] Backtrace
For further information, updates, and resolution to this issue, refer to KB article: vCenter Server Services hang on startup after upgrading to vCenter Server 5.1 (2035623).
--> Please see the VMware KB Page for the "solution" http://blogs.vmware.com/kb/2012/09/alert-vcenter-server-services-hang-on-startup-after-upgrading-to-vcenter-server-5-1.html