This one is driving me nuts, I have a virtual machine that randomly suspends itself. I checked the power options inside the VM, it's not set to any power plans (it should stay on).
I checked the logs on the host and there's no specific events that could've caused this, and the only thing I can see is within the vmx's log that the VMTools initiated the suspend call. I thought this was isolated to this particular VM, but the problem has spread to the other VMs right now, to a lesser frequency.
Environment:
Host: Windows 2008 Enterprise x64, VMWare Server 2, running 4 total Virtual Machine, Quad Core Xeon 2.8ghz, 16GB RAM
Guest: Windows 2003 Enterprise x86 SP2, using 2 proc threads, 2GB RAM, virtualized from physical machine by VMware vCenter.
Log from the vmx:
Mar 13 20:32:25.277: vmx| scsi0:0: Command WRITE(10) took 1.563 seconds (ok)
Mar 13 20:35:13.132: vmx| TOOLS sending 'OS_Suspend' (5) state change request
Mar 13 20:35:14.031: vcpu-0| TOOLS state change 5 returned status 1
Mar 13 20:35:14.036: vcpu-0| CPT current = 0, requesting 1
Mar 13 20:35:14.036: vcpu-0| Sync monModules(1).
Mar 13 20:35:14.036: vcpu-0| Done Sync monModules(1).
Mar 13 20:35:14.036: vcpu-1| Sync monModules(1).
Mar 13 20:35:14.036: vcpu-1| Done Sync monModules(1).
Mar 13 20:35:14.036: vmx| CPT: monitor ACKing mode 1
Mar 13 20:35:14.106: vmx| CPT current = 1, requesting 2
Mar 13 20:35:14.106: vmx| CPT: monitor ACKing mode 2
Mar 13 20:35:14.106: vmx| CPT current = 2, requesting 3
Mar 13 20:35:14.141: vcpu-0| Cpt monModules(3).
Mar 13 20:35:14.146: vcpu-0| Done Cpt monModules(3).
Mar 13 20:35:14.181: vcpu-1| Cpt monModules(3).
Mar 13 20:35:14.181: vcpu-1| Done Cpt monModules(3).
Mar 13 20:35:14.181: vmx| CPT: monitor ACKing mode 3
Mar 13 20:35:14.181: vmx| DUMPER: Modifying checkpoint file .\SBDIVAPP01.vmss
Mar 13 20:35:14.181: vmx| Checkpointed in VMware Server, 2.0.0 build-122956, build-122956, Windows Host
Mar 13 20:35:14.191: vmx| BusMemSample: checkpoint 3 initPercent 5 touched 52428
Mar 13 20:35:14.191: vmx| MM: Renamed D:\Virtual Machines\SBDIVAPP01\SBDIVAPP01.vmem to .\SBDIVAPP01.vmem
Mar 13 20:35:14.436: vmx| GuestMsg: Channel 0, Cannot unpost because the previous post is already completed
Mar 13 20:35:14.436: vmx| GuestRpc: Channel 0 reinitialized.
Mar 13 20:35:14.436: vmx| GuestMsg: Channel 1, Cannot unpost because the previous post is already completed
Mar 13 20:35:14.436: vmx| GuestRpc: Channel 1 reinitialized.
Mar 13 20:35:18.091: vmx| Stopping VCPU threads...
Mar 13 20:35:18.171: mks| SOCKET 3 (1624) recv error 10054: An existing connection was forcibly closed by the remote host
Mar 13 20:35:18.171: mks| SOCKET 3 (1624) destroying VNC backend on socket error: 1
Mar 13 20:35:18.176: mks| MKS switching absolute mouse off
Mar 13 20:35:19.096: mks| MKSHostOps_Exit3D: 1, 0
Mar 13 20:35:19.096: mks| Async MKS thread is exiting
Mar 13 20:35:19.096: vmx| USB: Disconnecting device 0x200000010e0f0002
Mar 13 20:35:19.096: vmx| USB: Disconnecting device 0x400000010e0f0003
Mar 13 20:35:19.116: vmx| MKS local poweroff
Mar 13 20:35:19.121: vmx| AIOWIN32C: asyncOps=929142 syncOps=0 bufSize=300Kb fixedOps=25681 sgOps=809264 sgOn=1
Mar 13 20:35:19.121: aioCompletion| AIO thread processed 929142 completions
Mar 13 20:35:19.121: vmx| AIOWIN32: asyncOps=0 syncOps=0 bufSize=0Kb delayed=0 fixed=0 sgOp=0 sgOn=1
Mar 13 20:35:19.121: vmx| WORKER: asyncOps=126192 maxActiveOps=1 maxPending=0 maxCompleted=0
Mar 13 20:35:19.641: vmx| Transitioned vmx/execState/val to suspended
Mar 13 20:35:19.966: vmx| vmdbPipe_Streams: Couldn't read
Mar 13 20:35:19.966: vmx| VMX idle exit
Mar 13 20:35:19.966: vmx| Flushing VMX VMDB connections
Mar 13 20:35:19.966: vmx| IPC_exit: disconnecting all threads
Mar 13 20:35:19.966: vmx| VMX exit (0).
Any help would be appreciated. Thanks. 