A virtual machine encounters an abrupt restart while the ESXi hypervisor remains stable. Log analysis indicates the Guest Operating System (OS) initiated a hardware reset request. This behavior is a protective response to underlying physical hardware faults, specifically DIMM failures, or critical resource exhaustion within the virtual graphics driver.
YYYY-MM-DDT##:##:##.###Z In(05) vcpu-0 - Chipset: The guest has requested that the virtual machine be hard reset.YYYY-MM-DDT##:##:##.###Z In(05) vcpu-1 - Guest: vmwgfx, warning: mob memory overflow.VMware vSphere ESXi 7.x / 8.x
If the guest operating system encounters a fatal internal error (eg: Machine Check Exception (MCE) or Kernel Panic) triggered by corrupted data originating from faulty/failing physical memory (DIMM), the guest OS sends a reset signal to the virtual chipset to maintain data integrity thus causing the VM to reboot.
vmware.log for the affected VM, execute the following command on the ESXi host CLI: vim-cmd vmsvc/getallvms/var/log/messages) for fatal exceptions matching the timestamp of the reboot.