vmware.log of the VM may show the NIC being quiesced, and then indication that the VMware Tools stopped responding shortly after2025-11-16T20:03:30.611Z In(05) vcpu-1 - VMXNET3 user: Quiesce device 0.2025-11-16T20:04:03.423Z In(05) vmx - GuestRpcSendTimedOut: message to toolbox timed out.2025-11-16T20:04:03.424Z In(05) vmx - Tools: [AppStatus] Last heartbeat value 52893 (last received 6s ago)2025-11-16T20:04:03.424Z In(05) vmx - TOOLS: appName=toolbox, oldStatus=1, status=2, guestInitiated=0.2025-11-16T20:04:18.072Z In(05) vcpu-0 - Tools: Tools heartbeat timeout.2025-11-16T20:04:18.073Z In(05) vcpu-0 - Tools: Running status rpc handler: 1 => 0.2025-11-16T20:04:18.073Z In(05) vcpu-0 - Tools: Changing running status: 1 => 0.2025-11-16T20:04:18.073Z In(05) vcpu-0 - Tools: [RunningStatus] Last heartbeat value 52893 (last received 20s ago)2025-11-16T20:04:23.425Z In(05) vmx - GuestRpcSendTimedOut: message to toolbox timed out.2025-11-16T20:04:43.426Z In(05) vmx - GuestRpcSendTimedOut: message to toolbox timed out.ESXi 8.x
VMware vCenter 8.x
This is most likely caused by a backup solution quiescing the VMs during a backup window. A guest OS and software application which is particularly busy may intermittently fail to make a timely response to a quiesce within the default time limit, preventing VMware Tools from successfully suspending I/O.