From upload log, it indicates that MKS stopped rendering and XP GOS was suspended later in vmware-0.log below.
...
2013-03-24T11:41:37.681-06:00| vmx| I120: GL-Backend: stopped by HWinMux to do window composition.
2013-03-24T11:41:37.681-06:00| vmx| I120: MKS-SWB: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 0.
2013-03-24T11:41:37.703-06:00| vmx| I120: GL-Backend: stopped by renderMux to do screen composition.
...
2013-03-24T11:42:31.020-06:00| vmx| I120: Tools: sending 'OS_Suspend' (state = 5) state change request <===this VM is suspended.
...
2013-03-24T11:42:37.679-06:00| mks| I120: GL-Backend: stopped by HWinMux to do window composition.
2013-03-24T11:42:37.679-06:00| mks| I120: MKS thread is exiting
Besides that, there is no obvious useful information to find the root cause. in order to narrow down this issue, I have the following question and action items.
Questions
=======
1.Any specific application software,especially, graphics related, used? or specific hardware attached?
2.Tools upgraded to latest version?
3. Is it pingable while this issue was reproduced?
once this issue is reproduced again, please help implement the following plan.
Action items
==========
1. Suspend the window XP GOS first, and Run vmss2core on the suspended state to get a Mac OS guest kernel core file referrring to this article:
http://kb.vmware.com/kb/2003941
2. Collect Fusion log through clicking Help manu> Collect Support Information. for details please refer to http://kb.vmware.com/kb/1003894
By the way, referring to Fusion 5.0.3 release notes, there is no obvious declaration to address this issue.
Best Regards,
changhai