Arnaud_L
Contributor
Contributor

VM Stop working with error: Handling vmx message 4543: VMware ESX unrecoverable error: (vcpu-6)

Jump to solution

Hi Everyone,

The other night, one of our VM shutdown by itself, without hardware overload . (ESXi 7.0.3 Build 19193900)

All I got from the log is this :

2022-03-29T21:29:50.281Z verbose hostd[2100486] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/5c35ae52-03e68016-00a6-801844ed6bca/Controller2/Controller2.vmx opID=esxui-5f8f-0b4c] Handling vmx message 4543: VMware ESX unrecoverable error: (vcpu-6)
--> A log file is available in "/vmfs/volumes/5c35ae52-03e68016-00a6-801844ed6bca/Controller2/vmware.log".
2022-03-29T21:29:50.282Z info hostd[2100485] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 332461 : An application (/bin/vmx) running on ESXi host has crashed (1 time(s) so far). A core file might have been created at /vmfs/volumes/5c35ae52-03e68016-00a6-801844ed6bca/Controller2/vmx-zdump.000.

I can provide on request the following files :

  • vmware-21.log
  • hostd.1.gz
  • vmx-zdump.000
0 Kudos
1 Solution

Accepted Solutions
abulhol
Enthusiast
Enthusiast
5 Replies
scott28tt
VMware Employee
VMware Employee

Thread reported so moderators know it should be moved to the ESXi/vSphere area, since you make no mention of an SDK.

 


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
0 Kudos
Arnaud_L
Contributor
Contributor

thanks, I honestly didn't find the good board for simply "vsphere" nor "esxi".

0 Kudos
abulhol
Enthusiast
Enthusiast

We had another crash like this yesterday.

We have no clue whether this is a hardware error or an issue with ESXi.

0 Kudos
ObjectifDubai
Enthusiast
Enthusiast

Hi, 

Can you check this KB, you may have a CPU problem on your Physical machine.

https://kb.vmware.com/s/article/50113028

 

0 Kudos
abulhol
Enthusiast
Enthusiast

We found that it's obviously this bug:
https://kb.vmware.com/s/article/86075

And it's resolved in the latest update release on March 29:
https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u3d-release-notes.html#resolvedissue...