I've noticed quite a few of our Hyper-V servers (both 2008 and 2012) report the following error in the Microsoft-Windows-Hyper-V-Hypervisor/Operational log when they restart (and start all the VMs):
Source: Hyper-V-Hypervisor
EventID: 8451
Text: Hyper-V failed creating a new partition (status 11)!
The various MS blogs I've Googled say the Status 11 error is just a general error meaning a VM couldn't be started. However all the VMs are running just fine. I suspect this may be a ghost VM left behind when a VM was deleted because if I take an HV server with three guests, all running fine, the last four events in the log show (in order):
Hyper-V failed creating a new partition (status 11)!
Hyper-V successfully created a new partition (partition 2).
Hyper-V successfully created a new partition (partition 3).
Hyper-V successfully created a new partition (partition 4).
So my guess is that there is a stub partition 1 left behind somewhere.
But I've looked and looked and cannot see any trace of an old partition 1 that might be causing the problem. Can anyone suggest where this might be, or alternatively is there some other explanation that I've overlooked?
Best Answer
It might be a resource alocation error. You might have a lot of resources alocated to the VM's and when they are starting then Windows can not alocate those resources fast enough(error 11) then it continues to boot them up.To test this I would: