Today a customer contacted me with a system consisting of 3 hosts running a VMware ESXi 5.0 cluster.
They were experiencing one, and only one VM, was complaining about configuration issues:
This virtual machine failed to become vSphere HA protected and HA may not attempt to restart it after a failure.
The customer had already tried to power down the VM and power on again, but unfortunately this had made no difference.
I disabled vSphere HA on the cluster:
After vSphere HA was deactivated on all hosts I simply went in and re-enabled vSphere HA on the cluster.
It took a few minutes for all the hosts to complete the tasks, but the VM was now finally protected:
As always, if this helped you please leave a comment 🙂
Incoming search terms:
- this virtual machine failed to become vsphere ha protected
- the virtual machine failed to become vsphere ha protected
- this virtual machine failed to become vsphere ha protected and ha may not attempt to restart it after a failure
- this virtual machine failed to become vsphere ha protected and ha may not attempt to restart
- virtual machine failed to become vsphere ha protected
- this virtual machine failed to become vsphere ha
- this virtual machine is not vsphere ha protected
Experienced the same problem at a customers site. Thanks for sharing!
Great to hear it helped you, thank you for taking time to comment! 🙂
Same problem at customer site, resolved. Thank you
Thank you for the feedback Nicola, very happy it helped you 🙂
This fixed my similar problem with ESXi 4.1 and ESXi 5.1. Thanks.
Do the VMs need to be powered off?
Hi Tom! No, you can do this while in production and VMs will keep running without issues.
Let me know if it solved your issue.
Same situation and this worked perfectly. Thanks for the post.
Stumbled across this blog post and it worked like a charm. Thanks!
hmm…from my point of view this is more a workaround, than a solution. The real question is, why does this happen? 🙂
hi friend,
i need a dumps for VCAC510
pls send on this email add:[email protected]