We have a Asus Clone PC that serves as our VM Machine Server haing these specifications:
Processor: Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz
4GB RAM
CentOS 5.1 Final
We are using VMServer 2.0.0 Build 116503
It was all fine way back the from the first time our 2 guest machines running simultaneously, when after 3 months, we encouter this error found in our log
Jan 11 13:26:03.501: vcpu-0| debugCtlLow: 0x1 debugCtlHigh: 0x0
Jan 11 13:26:03.501: vcpu-0| lastExceptionFromIP: 0xa7578, lastExceptionToIP: 0xa7592 excNum: 0x0
Jan 11 13:26:03.501: vcpu-0| MONITOR PANIC: vcpu-0:VMM fault: regs=0x2a20, exc=14, eip=0xa75a8
Jan 11 13:26:03.501: vcpu-0| Core dump with build build-116503
Jan 11 13:26:03.501: vcpu-0| Writing monitor corefile "/var/lib/vmware/Virtual Machines/mclr01headlin/vmware-core.gz"
Jan 11 13:26:03.501: vcpu-0| CoreDump: dumping core with superuser privileges
Jan 11 13:26:04.075: vcpu-0| Saving busmem frames
Jan 11 13:26:04.075: vcpu-0| Saving anonymous memory
Jan 11 13:26:04.080: vcpu-0| Beginning monitor coredump
Jan 11 13:26:04.899: vcpu-0| End monitor coredump
Jan 11 13:26:04.899: vcpu-0| Beginning extended monitor coredump
Jan 11 13:26:04.899: vcpu-0| Writing anonymous pages at pos: 401000
Jan 11 13:26:09.672: vcpu-0| Core dump limit is 0 KB.
Jan 11 13:26:09.674: vcpu-0| Child process 19676 failed to dump core (status 0x6).
Jan 11 13:26:09.675: vcpu-0| Msg_Post: Error
Jan 11 13:26:09.675: vcpu-0| http://msg.log.monpanic *** VMware Server internal monitor error ***
Jan 11 13:26:09.675: vcpu-0| vcpu-0:VMM fault: regs=0x2a20, exc=14, eip=0xa75a8
Jan 11 13:26:09.675: vcpu-0| http://msg.log.monpanic.report Please report this problem by selecting menu item Help > VMware on the Web > Request Support, or by going to the Web page "http://vmware.com/info?id=8&logFile=%2fvar%2flib%2fvmware%2fVirtual%20Machines%2fmclr01headlin%2fvmware%2elog&coreLocation=%2fvar%2flib%2fvmware%2fVirtual%20Machines%2fmclr01headlin%2fvmware%2dcore%2egz". Please provide us with the log file (/var/lib/vmware/Virtual Machines/mclr01headlin/vmware.log) and the core file(s) (/var/lib/vmware/Virtual Machines/mclr01headlin/vmware-core.gz).
Jan 11 13:26:09.675: vcpu-0| http://msg.log.monpanic.linuxdebug If the problem is repeatable, please set 'Logging level' to 'Debug' in the 'Misc' panel of Virtual Machine Settings. Then reproduce the incident and file it according to the instructions.
Jan 11 13:26:09.675: vcpu-0| http://msg.log.monpanic.vmSupport.windowsOrLinux To collect data to submit to VMware support, select Help > About and click "Collect Support Data". You can also run the "vm-support" script in the Workstation folder directly.
Jan 11 13:26:09.675: vcpu-0| http://msg.log.monpanic.entitlement We will respond on the basis of your support entitlement.
Jan 11 13:26:09.675: vcpu-0| http://msg.log.monpanic.finish We appreciate your feedback,
Jan 11 13:26:09.675: vcpu-0| -- the VMware Server team.
Jan 11 13:26:09.675: vcpu-0| -
Jan 11 13:26:09.677: vcpu-0| Exiting vcpu-0
Jan 11 13:26:09.685: Worker#16| VTHREAD watched thread 4 "vcpu-0" died
Jan 11 13:26:09.685: Worker#17| VTHREAD watched thread 4 "vcpu-0" died
Jan 11 13:26:09.686: Worker#7| VTHREAD watched thread 4 "vcpu-0" died
Jan 11 13:26:09.687: Worker#8| VTHREAD watched thread 4 "vcpu-0" died
Jan 11 13:26:09.688: Worker#12| VTHREAD watched thread 4 "vcpu-0" died
Jan 11 13:26:09.697: Worker#13| VTHREAD watched thread 4 "vcpu-0" died
Jan 11 13:26:09.697: Worker#10| VTHREAD watched thread 4 "vcpu-0" died
Jan 11 13:26:09.698: Worker#15| VTHREAD watched thread 4 "vcpu-0" died
Jan 11 13:26:09.698: Worker#9| VTHREAD watched thread 4 "vcpu-0" died
Jan 11 13:26:09.699: Worker#5| VTHREAD watched thread 4 "vcpu-0" died
Jan 11 13:26:09.699: Worker#14| VTHREAD watched thread 4 "vcpu-0" died
Jan 11 13:26:09.699: Worker#11| VTHREAD watched thread 4 "vcpu-0" died
Jan 11 13:26:09.748: Worker#6| VTHREAD watched thread 4 "vcpu-0" died
Jan 11 13:26:10.675: vmx| VTHREAD watched thread 4 "vcpu-0" died
Jan 11 13:26:10.685: Worker#3| VTHREAD watched thread 0 "vmx" died
Jan 11 13:26:10.686: Worker#4| VTHREAD watched thread 0 "vmx" died
Jan 11 13:26:10.687: Worker#2| VTHREAD watched thread 0 "vmx" died
Jan 11 13:26:10.698: Worker#1| VTHREAD watched thread 0 "vmx" died
Jan 11 13:26:10.744: usbCCIDEnumCards| VTHREAD watched thread 0 "vmx" died
Jan 11 13:26:10.747: Worker#0| VTHREAD watched thread 0 "vmx" died
Jan 11 13:26:10.777: mks| VTHREAD watched thread 0 "vmx" died
What would be our primary response with this problem? how do we fixed this and preent from coming back?
Any Information is highly apprecaited.. thanks
anthony