Ok, before I raise a support call for this, thought I'd run it pass here first.
I have a test VM which I have created a snapshot for and installed software. I then decided that I didn't want it setup quite like that and chose "Revert to Snapshot". The VM was placed into a suspended state while it did it's stuff and then came up with a "Error encountered while trying to restore the state of group monitorLate from file .....(/vmfs path)....Snapshot1.vmsn"
I cannot get the VM out of suspended state - power on is the only option and I get the same message if I try that.
Details from vmware.log are
May 14 09:33:53.217: vmx| restoring VGA
May 14 09:33:53.227: vmx| restoring DMA
May 14 09:33:53.228: vmx| restoring BackdoorAPM
May 14 09:33:53.228: vmx| restoring CMOS
May 14 09:33:53.228: vmx| restoring FlashRam
May 14 09:33:53.230: vmx| restoring A20
May 14 09:33:53.230: vmx| restoring Keyboard
May 14 09:33:53.231: vmx| restoring backdoorAbsMouse
May 14 09:33:53.231: vmx| restoring SIO
May 14 09:33:53.231: vmx| restoring serial0
May 14 09:33:53.231: vmx| restoring serial1
May 14 09:33:53.231: vmx| restoring serial2
May 14 09:33:53.231: vmx| restoring serial3
May 14 09:33:53.231: vmx| restoring parallel0
May 14 09:33:53.231: vmx| restoring parallel1
May 14 09:33:53.231: vmx| restoring parallel2
May 14 09:33:53.231: vmx| restoring SVGA
May 14 09:33:53.235: vmx| SVGA phys sizes: 1180x885x32 offset 0 fb 0x00400000
May 14 09:33:53.235: vmx| SVGA compatible geometry on checkpoint restore
May 14 09:33:53.235: vmx| SVGA old geometry 1180x885, max size = 4194304
May 14 09:33:53.235: vmx| SVGA new geometry 1180x885, max size = 4194304
May 14 09:33:53.347: vmx| restoring Ethernet0
May 14 09:33:53.347: vmx| restoring monitorLate
May 14 09:33:53.347: vmx| Msg_Post: Error
May 14 09:33:53.347: vmx| \[msg.checkpoint.restoregroup.fail] Error encountered while trying to restore the state of group
monitorLate from file "/vmfs/volumes/44ac8000-abaefe3e-10c2-000423b8744f/mschcctxptst01/mschcctxptst01-Snapshot1.vmsn".
May 14 09:33:53.347: vmx| \----
May 14 09:33:53.352: vmx| Module CheckpointLate power on failed.
May 14 09:33:53.352: vmx| VMX_PowerOn: ModuleTable_PowerOn = 0
May 14 09:33:53.361: vmx| MKS local poweroff
May 14 09:33:53.363: vmx| Lock before MKS lock created. Early poweroff?
May 14 09:33:53.363: vmx| Unlock before MKS lock created. Early poweroff?
May 14 09:33:53.364: vmx| scsi0:0: numIOs = 0 numMergedIOs = 0 numSplitIOs = 0 ( 0.0%)
May 14 09:33:53.364: vmx| DISKLIB-VMFS :
"/vmfs/volumes/44ac8000-abaefe3e-10c2-000423b8744f/mschcctxptst01/mschcctxptst01-000002-delta.vmdk" : closed.
May 14 09:33:53.365: vmx| DISKLIB-VMFS :
"/vmfs/volumes/44ac8000-abaefe3e-10c2-000423b8744f/mschcctxptst01/mschcctxptst01-flat.vmdk" : closed.
May 14 09:33:54.662: vmx| vmdbPipe_Streams Couldn't read: OVL_STATUS_EOF
May 14 09:33:54.662: vmx| VMX idle exit
May 14 09:33:54.669: vmx| Flushing VMX VMDB connections
May 14 09:33:54.674: vmx| IPC_exit: disconnecting all threads
May 14 09:33:54.674: vmx| VMX exit.
May 14 09:33:54.674: vmx| AIOMGR-S : stat o=2 r=0 w=0 i=6 br=0 bw=0[/code]
Any ideas on where I should look / what I should try for this?
Thanks
Darren
