Thursday, June 18, 2015

'Virtual Machine' failed to start on Windows Server 2008 R2 Hyper-V

Many of Hyper-V administrators may get this error when power on a virtual machine.

'Virtual Machine name' failed to start. (Virtual Machine ID XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX)

You can find the error event, ID 12030, on Hyper-V-Worker folder of Event Viewer but there is no more additional information. 

One of the reason that the virtual machine cannot be started up is there is not enough memory on the Hyper-V host to start up virtual machine. Many of you may know this answer. 

How come there is not enough memory?
I could start up the virtual machine normally.

One of my experience is the Hyper-V host might copy a large file and the cached the memory for hardware RAID controller. The Hyper-V host cached a lot of memory so I couldn't start up the virtual machine after power off.

To solve this issue, we can check how many memory is available on the host. Then, we can modify the start up memory size of the virtual machine which is less than the existing one. After that, try to power on the virtual machine.

It's not a new troubleshooting skill but we may forget it. That's why I'd like to share it.


This posting is provided “AS IS” with no warranties, and confers no rights!

No comments:

Post a Comment