Today, something weird happen. 1 of my VM guest which is windows 2003 server suddenly hung up. When I try to reset it, the Console screen show blank after the bios screen. I try to attach the VMDK to another newly created VM and it still not functioning. To verify the vmdk is not corrupted, I mount the vmdk to another windows 2003 VM and I found that the VMDK is functioning.

After that, I try to check most of the setting and log file from putty and virtual center. Here is my finding. Due to some unknown reason, the .vmx file setting and the configuration on the virtual center show really different. I had to force restart the virtual center service, and reconfigure some of the resources setting in virtual center to ensure it had not reserve or limit any resources on CPU and memory, and I power up the VM again. This round, the VM able to power up and functioning. Originally, It shouldn’t reserve any resource as I had not configured that. For some unknown reason, the resources limit had been configured by the ESX itself. This had happened in the pass but it had not cause any issue.

The root cause here is clear again that the virtual center information is not tally with the information from the command. I will say this is not something new and is well known and really causing so much issue sometimes. A lesson really had been learnt today.