VMware vSphere

 View Only
  • 1.  vSphere HA virtual machine error

    Posted Feb 18, 2013 04:11 PM

    Dear All,

    I have a cluster with 3 ESXi hosst.

    I have for only one VM a vsphere HA virtual machine error followed by vsphere HA virtual machine action alarm.

    Could you please help me to fix this error? The error comes up a few days later after I cleared it.

    Thank you,

    Edy



  • 2.  RE: vSphere HA virtual machine error

    Posted Feb 18, 2013 04:13 PM

    Note: Discussion successfully moved from VMware vCenter™ Server to Availability: HA & FT

    What is the exact error message you are seeing?



  • 3.  RE: vSphere HA virtual machine error

    Posted Feb 18, 2013 04:13 PM

    Please post a screenshot of error. Also are other VMs on the same Host OK ?



  • 4.  RE: vSphere HA virtual machine error

    Posted Feb 18, 2013 04:35 PM

    Yes there are other VM on the same host without a problem.

    I post the screenshot as requested.

    Thanks,

    Edy



  • 5.  RE: vSphere HA virtual machine error

    Broadcom Employee
    Posted Feb 18, 2013 04:40 PM

    Just acknowledge the Alarm. This is triggered when for whatever reason the reset of a VM has failed. I guess it is still stuck there.



  • 6.  RE: vSphere HA virtual machine error

    Posted Feb 18, 2013 04:45 PM

    I do acknowledge the alarm, but it comes up after a few days again and again.

    This is the reason why I thought to seek help in this community.



  • 7.  RE: vSphere HA virtual machine error

    Posted Feb 18, 2013 06:25 PM

    Can you check the "events" tab for the vm to see what HA event triggered this alarm?



  • 8.  RE: vSphere HA virtual machine error

    Posted Feb 22, 2013 10:39 AM

    Do you still have an issue or is it resolved ?



  • 9.  RE: vSphere HA virtual machine error

    Posted Feb 25, 2013 09:45 AM

    Since I acknowledged the alarm 5 days ago, I haven't had another alarm. It's a bit weird,  because before I posted the problem here, I have had acknowledged the alarm a few times and it always came back.

    So for the moment it appears the problem is solved.