2023-01-29T08:07:15.232Z In(05) vcpu-0 - Vix: [vmxCommands.c:7182]: VMAutomation_HandleCLIHLTEvent. Do nothing.
2023-01-29T08:07:15.232Z In(05) vcpu-0 - MsgHint: msg.monitorevent.halt
2023-01-29T08:07:15.232Z In(05)+ vcpu-0 - The CPU has been disabled by the guest operating system. Power off or reset the virtual machine.
2023-01-29T08:07:15.232Z In(05)+ vcpu-0 - ---------------------------------------
2023-01-29T08:07:15.235Z In(05) vcpu-0 - VigorTransportProcessClientPayload: opID=vim-cmd-6d-8fa4 seq=49288: Receiving Bootstrap.MessageReply request.
NOTE: This KB is not be used for any other VM soft lockup issue.
NOTE:The preceding log excerpts are only examples.Date,time and environmental variables may vary depending on your environment.
Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice or statements made on third-party websites.Inclusion of such links does not imply that VMware endorses,recommends or accepts any responsibility for the content of such sites.
This issue is mitigated in VMware vSphere ESXi 7.0 U3n and ESXi 8.0 U1c patches. To download go to the Customer Connect Patch Downloads page.
To workaround use one of the below steps to disable VMX logging for 3rd party Hyper Converged Infrastructure controller VM's.
1. Disabling virtual machine logging (For 3rd party Hyper Converged Infrastructure controller VM's) using SSH.
2. From GUI - To configure the disable logging option:
Example: