oner of my VMs went down today for no reason, or at least no reason that I can find.
Anyone has seen this before ?
Machine powered off as soon as I atempted to start it.
This is the vmware-serverd.log
New connection on socket server-vmdb from host torcagsx4.atitech.com (ip address: 127.0.0.1) , user: %username%
Aug 15 12:25:41: app| SP: New user session for user: %username%, pos: 0
Aug 15 12:25:42: app| The vm-list file has changed! Reloading the list of registered vms
Aug 15 12:25:42: app| Attempt to violate field protection bit: /host2/#711c67d46dd2fbca/info/nic/nicHardwareCount/
Aug 15 12:25:56: app| vmdbPipe_Streams: Couldn't read
Aug 15 12:25:56: app| IPC Socket read error 10054
Aug 15 12:25:56: app| VMServerd IPC closed the connection with thread C:\Virtual Machines\lcs\torcalcs2\winNetStandard.vmx (00A800F0)
Aug 15 12:25:56: app| Lost connection to C:\Virtual Machines\lcs\torcalcs2\winNetStandard.vmx (C:\Virtual Machines\lcs\torcalcs2\winNetStandard.vmx) unexpectedly.
Aug 15 12:25:56: app| VMHS: Connection to VM broken: cfg: C:\Virtual Machines\lcs\torcalcs2\winNetStandard.vmx; error: Pipe: Read failed; state: 3
Aug 15 12:25:56: app| SP: Retrieved username: %username%
Aug 15 12:25:57: app| Running VM using local system account
Aug 15 12:25:57: app| cleanup: cleaned up 2 objects
Aug 15 12:25:57: app| VM suddenly changed state: poweredOff.
Aug 15 12:25:57: app| VM suddenly changed state: poweredOff.
Aug 15 12:25:57: app| VM suddenly changed state: poweredOff.
Aug 15 12:25:57: app| System.WaitToKillServiceTimeout = 950
Aug 15 12:25:57: app| System.WaitToKillServiceTimeout = 950
Aug 15 12:25:57: app| System.WaitToKillServiceTimeout = 950
Aug 15 12:25:57: app| System.WaitToKillServiceTimeout = 950
Aug 15 12:25:59: app| VM suddenly changed state: poweredOff.
Aug 15 12:26:14: app| Running VM using local system account
Aug 15 12:26:14: app| Attempting to launch vmx : C:\Virtual Machines\lcs\torcalcs2\winNetStandard.vmx