Rasmus Haslund

Virtualize everything!

  • LinkedIn
  • RSS
  • Twitter
  • YouTube
  • Home
  • Videos
  • Practice Exams
    • VMCE practice exam – Veeam Certified Engineer
  • EqualLogic
  • Veeam
  • VMware
  • About

VMware ESXi Single VM is not vSphere HA protected

2013-02-13 by Rasmus Haslund 11 Comments

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:
VM_not_vsphere_ha_protected
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:
VM_not_vsphere_ha_protected_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:
VM_not_vsphere_ha_protected_ok

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

Filed Under: Fix IT, VMware Tagged With: ESXi, fails, ha, VMware, vSphere

Subscribe
Login
Notify of
Please login to comment
11 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
Christophe Jacob
12 years ago

Experienced the same problem at a customers site. Thanks for sharing!

1
Rasmus Haslund
12 years ago
Reply to  Christophe Jacob

Great to hear it helped you, thank you for taking time to comment! 🙂

0
Nicola Papapicco
12 years ago

Same problem at customer site, resolved. Thank you

0
Rasmus Haslund
12 years ago
Reply to  Nicola Papapicco

Thank you for the feedback Nicola, very happy it helped you 🙂

0
Paul Xu
12 years ago

This fixed my similar problem with ESXi 4.1 and ESXi 5.1. Thanks.

0
Tom Paget
11 years ago

Do the VMs need to be powered off?

0
Rasmus Haslund
11 years ago
Reply to  Tom Paget

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.

0
Rod Lewis
11 years ago

Same situation and this worked perfectly. Thanks for the post.

0
Adrian Ryan SanMiguel
11 years ago

Stumbled across this blog post and it worked like a charm. Thanks!

0
Enrico Steppat Laursen
11 years ago

hmm…from my point of view this is more a workaround, than a solution. The real question is, why does this happen? 🙂

0
pankaj
9 years ago

hi friend,
i need a dumps for VCAC510
pls send on this email add:[email protected]

0

Sponsors

wpDiscuz