![]() Jun 22 22:24:31: mks| VTHREAD watched thread 0 "vmx" died Jun 22 22:24:31: vmx| VTHREAD thread 0 exiting, 5 left Jun 22 22:24:31: vmx| VTHREAD thread 0 start exiting Jun 22 22:24:31: vmx| VTHREAD watched thread 4 "vcpu-0" died Jun 22 22:24:30: vcpu-0| VTHREAD thread 4 exiting, 6 left Jun 22 22:24:30: vcpu-0| VTHREAD thread 4 start exiting Jun 22 22:24:30: vcpu-0| Ignoring broadcast request ![]() Jun 22 22:24:30: mks| VTHREAD create thread 4 "kbh" Jun 22 22:24:30: kbh| VTHREAD thread 4 "kbh" host id 1928 started Jun 22 22:22:51: mks| VTHREAD destroy thread 4 "kbh" Jun 22 22:22:51: vcpu-0| - the VMware Workstation team. Jun 22 22:22:51: vcpu-0| We appreciate your feedback, Jun 22 22:22:51: vcpu-0| We will respond on the basis of your support entitlement. Then reproduce the incident and file it according to the instructions. Jun 22 22:22:51: vcpu-0| If the problem is repeatable, please select 'Run with debugging information' in the Options panel of the configuration editor. Please provide us with the log file (C:\Documents and Settings\keyoke\My Documents\My Virtual Machines\MS-DOS\vmware.log) and the core file (C:\Documents and Settings\keyoke\My Documents\My Virtual Machines\MS-DOS\vmware-core.gz). Jun 22 22:22:51: vcpu-0| Please report this problem by selecting menu item Help > VMware on the Web > Request Support, or by going to the Web page "". Jun 22 22:22:51: vcpu-0| *** VMware Workstation internal monitor error *** Jun 22 22:22:50: vcpu-0| Writing monitor corefile "C:\Documents and Settings\keyoke\My Documents\My Virtual Machines\MS-DOS\vmware-core.gz"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |