Host: 10.8.5 Guest : Mavericks DP 7 Parallels : 9.0.23062 When the guest Mavericks goes to sleep, and you click on RESUME, the VM crashes without any message.
The LOG file shows following entries 09-15 11:09:18.773 F /vm:11558:a803/ VCPU1 state(VcpuStateStopped): changed to VcpuStateRunning 09-15 11:09:18.773 F /vm:11558:a803/ VCPU1 state(VcpuStateRunning): completed 'VcpuCmdRun'(2) command with result 0x0 [1] HostRet: t=4322934556 req=8 (gt=9927166) Activating Unrestricted Guest on VCPU 1 09-15 11:09:18.773 F /vm:11558:a803/ VM state(VmStatePaused): enqueued 'VmLocalEventCpuStopped'(20031) command 09-15 11:09:18.773 F /vm:11558:a803/ VCPU1 state(VcpuStateRunning): changed to VcpuStateStopped 09-15 11:09:18.827 F /vm:11558:3a03/ VM state(VmStatePaused): changed to VmStateRunning 09-15 11:09:18.827 F /vm:11558:3a03/ VM state(VmStateRunning): completed 'VmLocalCmdStart'(20001) command with result 0x0 09-15 11:09:18.828 F /vm:11558:3a03/ VM state(VmStateRunning): completed 'VmLocalEventCpuUnpaused'(20033) command with result 0x0 09-15 11:09:18.829 F /vm:11558:3a03/ VM state(VmStateRunning): completed 'DspVmStateInfo'(3028) command with result 0x0 09-15 11:09:18.829 F /vm:11558:3a03/ VM state(VmStateRunning): completed 'VmLocalEventCpuStopped'(20031) command with result 0x0 09-15 11:09:18.834 F /vm:11558:2d03/ VM state(VmStateRunning): enqueued 'DspVmStateInfo'(3028) command 09-15 11:09:18.834 F /vm:11558:3a03/ VM state(VmStateRunning): completed 'DspVmStateInfo'(3028) command with result 0x0 09-15 11:09:18.837 W DYNRESHOST /vm:11558:bc03/ Startup information. Host has hidpi display: 0 Acpi: going to sleep type 7 09-15 11:09:59.913 F /vm:11558:a213/ SHUTDOWN: type 0x21 VCPU=0 09-15 11:09:59.913 F /vm:11558:a213/ VM state(VmStateRunning): enqueued 'VmLocalCmdStop'(20011) command 09-15 11:09:59.913 F /vm:11558:a213/ VCPU0 state(VcpuStateRunning): enqueued 'VcpuCmdTerminate'(6) command 09-15 11:09:59.913 F /vm:11558:a213/ VCPU1 state(VcpuStateStopped): enqueued 'VcpuCmdTerminate'(6) command 09-15 11:09:59.913 F /vm:11558:a213/ VCPU0 state(VcpuStateRunning): changed to VcpuStateTerminated 09-15 11:09:59.913 F /vm:11558:a213/ VCPU0 state(VcpuStateTerminated): completed 'VcpuCmdTerminate'(6) command with result 0x0 09-15 11:09:59.913 F /vm:11558:a803/ VCPU1 state(VcpuStateStopped): changed to VcpuStateTerminated 09-15 11:09:59.913 F /vm:11558:a803/ VCPU1 state(VcpuStateTerminated): completed 'VcpuCmdTerminate'(6) command with result 0x0 09-15 11:09:59.913 F /vm:11558:3a03/ SARE state(SareStateStart): enqueued 'SareCmdTerminate'(8) command 09-15 11:09:59.913 F /vm:11558:3a03/ VM state(VmStateRunning): changed to VmStateStopped 09-15 11:09:59.913 F /vm:11558:3903/ SARE state(SareStateStart): completed 'SareCmdTerminate'(8) command with result 0x80000009 09-15 11:09:59.914 F /vm:11558:3a03/ Terminating CPU #1 ... 09-15 11:09:59.914 F /vm:11558:3a03/ VCPU1 state(VcpuStateTerminated): enqueued 'VcpuCmdTerminate'(6) command 09-15 11:09:59.914 F /vm:11558:3a03/ Terminating CPU #0 ... 09-15 11:09:59.914 F /vm:11558:3a03/ VCPU0 state(VcpuStateTerminated): enqueued 'VcpuCmdTerminate'(6) command
Thanks to Parallels Support team. The issue was with the Parallels Tools. When you install the tools first time, there is a warning of SIGNING on KEXT. But in fact the KEXT's are not installed. After reboot, reinstall Parallel Tools and if there is no warning, things work beautifully. No crash in last 4 hours