RCA 35: VM Rebooted Unexpectedly on ESXi Host

Post category:Logs Analysis / VMware Analysis
Post published:July 29, 2024
Post last modified:July 30, 2024

1) wxyzoteng2a

SGT- 22nd, 2:58:19am

UTC – 21st 6:58pm

2) wxyzoisrv1a

SGT – 22nd 6:18:23am

UTC – 21st 10:18pm

Hostname: abcdefent1201a.vpc.sgp.abc.com

ESXi Version: ESXi 6.7 P02

Time of Restart:

SGT – 22nd 6:18:23am

UTC – 21st 10:18pm

VM Name: wxyzoisrv1a

Here we can see a VM Hard reset Operation being Triggered:

2021-02-21T22:18:39.800Z| vcpu-0| W115: Balloon: Start: vmmemctl reset balloon
2021-02-21T22:18:23.304Z| vcpu-0| I125: VigorTransport_ServerSendResponse opID=lro-224-50f8a991-SWI-6a5f15b7-4ed9 seq=10274741: Completed PowerState request.

Hostd Logs:

From the Hostd Logs we can see a Reset operation triggered for the Virtual Machine:

2021-02-21T22:14:28.830Z info hostd[2101747] [Originator@6876 sub=Vimsvc.TaskManager opID=lro-224-50f8a991-SWI-6a5f15b7-4ed9 user=vpxuser] Task Created : haTask-65-vim.VirtualMachine.reset-2637415330
2021-02-21T22:14:28.831Z info hostd[2102497] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=lro-224-50f8a991-SWI-6a5f15b7-4ed9 user=vpxuser] Event 58179 : wxyzoisrv1a on abcdefent1201a.vpc.sgp.abc.com in ha-datacenter is reset
2021-02-21T22:14:28.831Z info hostd[2102497] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/5d8378f5-0b8e6872-da93-e4434b82daac/wxyzoisrv1a/wxyzoisrv1a.vmx opID=lro-224-50f8a991-SWI-6a5f15b7-4ed9 user=vpxuser] State Transition (VM_STATE_ON -> VM_STATE_RESETTING)

VPXA Logs:

Has been rolled over.

Hostname: abcdefent1159a.vpc.sgp.abc.com

ESXi Version: ESXi 6.7 P02

Time of Issue:

SGT- 22nd, 2:58:19am

UTC – 21st 6:58pm

VM Name: Wxyzoteng2a

2021-02-21T18:58:18.827Z| vcpu-0| I125: VigorTransport_ServerSendResponse opID=lro-2582-5e41c20a-SWI-29fe903-8f6e seq=8916140: Completed PowerState request.

VPXA Logs:

Logs have been rolled over:

Conclusion:

Based on the logs we can say that the Virtual Machines has undergone a reset and it seems like being triggered by the vCenter HA.

As per the Article: https://kb.vmware.com/s/article/1019064 Pointer 9.

Determine if the virtual machine was restarted by High Availability Virtual Machine Monitoring.

Review the vmware.log for the affected virtual machine (/vmfs/volumes/<datastore>/<VM directory>/vmware.log), you will see entries similar to:

vmx| Vix: [104333 vmxCommands.c:457]: VMAutomation_Reset. Trying hard reset

Since the VPXA logs have been rolled over we are not able to find the tasks and events under which the VPX service.

Action Plan:

Please check if there is VM Monitoring is enabled in the vCenter Server ?
Please check if there is any Tasks and events shown under the vCenter server for the Virtual Machine because the reset operation is triggered.
Please Capture and share with me the Support bundle for the vCenter Server so that I can look into the logs of the VPXD Service and check if there is any more information present

Ashutosh Dixit

I am currently working as a Senior Technical Support Engineer with VMware Premier Services for Telco. Before this, I worked as a Technical Lead with Microsoft Enterprise Platform Support for Production and Premier Support. I am an expert in High-Availability, Deployments, and VMware Core technology along with Tanzu and Horizon.