Hello.
I have used VMware server for most of time for testing purposes and it worked great. Now on a production server it has started to crash. I am trying to debug the problem but I need some help about it. I don't wish to reinstall the system in anyway.
I am using the following:
VMware Server 2.0.2.
Centos 5.2 (with updates) 64bit
-have read someting about glibc problems ( I seem to have that version that causes trouble) but I am unsure.
Host is 64bit.
Guest is 32bit.
Guest OS is Windows Server 2008 Standard with MSSQL 2008 Standard
Error is : Unexpected signal: 11
Error looks like this:
Apr 16 22:57:28.506: vmx| Caught signal 11 -- tid 13728
Apr 16 22:57:28.506: vmx| SIGNAL: eip 0x38b8a6f8d8 esp 0x7fff29388c80 ebp 0x1a5bb130
Apr 16 22:57:28.506: vmx| SIGNAL: eax 0xf0000001a5bb110 ebx 0x1a5bb140 ecx 0x40 edx 0xf100000000000020 esi 0x1 edi 0x1a5bb140
Apr 16 22:57:28.506: vmx| r8 0x0 r9 0x40000 r10 0x0 r11 0x38b8a7b17c r12 0x0 r13 0x0 r14 0x0 r15 0x1
Apr 16 22:57:28.506: vmx| SIGNAL: stack 7FFF29388C80 : 0x00000000 0x00000000 0x1a5bb140 0x00000000
Apr 16 22:57:28.506: vmx| SIGNAL: stack 7FFF29388C90 : 0x00000000 0x00000000 0x00000800 0x00000000
Apr 16 22:57:28.506: vmx| SIGNAL: stack 7FFF29388CA0 : 0x00000000 0x00000000 0xb8a75c82 0x00000038
Apr 16 22:57:28.506: vmx| SIGNAL: stack 7FFF29388CB0 : 0x1a305410 0x00000000 0x00edbcd0 0x00000000
Apr 16 22:57:28.506: vmx| SIGNAL: stack 7FFF29388CC0 : 0x00010000 0x00000000 0x19fe6640 0x00000000
Apr 16 22:57:28.506: vmx| SIGNAL: stack 7FFF29388CD0 : 0x19ce1a40 0x00000000 0x00000000 0x00000000
Apr 16 22:57:28.506: vmx| SIGNAL: stack 7FFF29388CE0 : 0x00000800 0x00000000 0xb8a727c1 0x00000038
Apr 16 22:57:28.506: vmx| SIGNAL: stack 7FFF29388CF0 : 0x00000000 0x00000000 0x19ce1a40 0x00000000
.... backtrace ...
Apr 16 22:57:28.507: vmx| Unexpected signal: 11.
Apr 16 22:57:28.507: vmx| Core dump limit is 0 KB.
Apr 16 22:57:28.512: vmx| Child process 18652 failed to dump core (status 0x6).
...
Apr 16 22:57:28.513: vmx| Msg_Post: Error
Apr 16 22:57:28.513: vmx| http://msg.log.error.unrecoverable VMware Server unrecoverable error: (vmx)
Apr 16 22:57:28.513: vmx| Unexpected signal: 11.
Apr 16 22:57:28.513: vmx| http://msg.panic.haveLog A log file is available in "/var/lib/vmware/Virtual Machines/VPS-RentWay/vmware.log". http://msg.panic.requestSupport.withLog Please request support and include the contents of the log file. http://msg.panic.requestSupport.vmSupport.windowsOrLinux
Apr 16 22:57:28.513: vmx| 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.
Apr 16 22:57:28.513: vmx| http://msg.panic.response We will respond on the basis of your support entitlement.
Apr 16 22:57:28.513: vmx| -
Apr 16 22:57:28.513: vmx| POST(no connection): VMware Server unrecoverable error: (vmx)
Apr 16 22:57:28.513: vmx| Unexpected signal: 11.
Apr 16 22:57:28.513: vmx| A log file is available in "/var/lib/vmware/Virtual Machines/VPS-RentWay/vmware.log". Please request support and include the contents of the log file.
Apr 16 22:57:28.513: vmx| 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.
Apr 16 22:57:28.513: vmx| We will respond on the basis of your support entitlement.
Apr 16 22:57:28.513: vmx|
Apr 16 22:57:28.593: usbCCIDEnumCards| VTHREAD watched thread 0 "vmx" died
Apr 16 22:57:28.613: Worker#6| VTHREAD watched thread 0 "vmx" died
Apr 16 22:57:28.614: mks| VTHREAD watched thread 0 "vmx" died
Apr 16 22:57:28.617: Worker#5| VTHREAD watched thread 0 "vmx" died
Apr 16 22:57:28.617: Worker#3| VTHREAD watched thread 0 "vmx" died
Apr 16 22:57:28.622: Worker#0| VTHREAD watched thread 0 "vmx" died
Apr 16 22:57:28.622: Worker#2| VTHREAD watched thread 0 "vmx" died
Apr 16 22:57:29.007: vcpu-0| VTHREAD watched thread 0 "vmx" died
Apr 16 22:57:29.013: Worker#9| VTHREAD watched thread 4 "vcpu-0" died
Apr 16 22:57:29.017: Worker#10| VTHREAD watched thread 4 "vcpu-0" died
Apr 16 22:57:29.019: Worker#1| VTHREAD watched thread 4 "vcpu-0" died
Apr 16 22:57:29.019: Worker#15| VTHREAD watched thread 4 "vcpu-0" died
Apr 16 22:57:29.019: Worker#7| VTHREAD watched thread 4 "vcpu-0" died
Apr 16 22:57:29.022: Worker#14| VTHREAD watched thread 4 "vcpu-0" died
Apr 16 22:57:29.022: Worker#8| VTHREAD watched thread 4 "vcpu-0" died
Apr 16 22:57:29.022: Worker#12| VTHREAD watched thread 4 "vcpu-0" died
Apr 16 22:57:29.022: Worker#11| VTHREAD watched thread 4 "vcpu-0" died
Apr 16 22:57:29.022: Worker#16| VTHREAD watched thread 4 "vcpu-0" died
Apr 16 22:57:29.022: Worker#17| VTHREAD watched thread 4 "vcpu-0" died
Apr 16 22:57:29.022: Worker#4| VTHREAD watched thread 4 "vcpu-0" died
Apr 16 22:57:29.023: Worker#13| VTHREAD watched thread 4 "vcpu-0" died
-EOL
This happens often.
-i am thinking about:
-USB device (HASP KEY) - maybe doesn't like the device
-Direct 3D (to disable )
-glibc downgrade (http://ccforums.clearfoundation.com/showthreaded.php?Number=121752)
-SCSI (LSI SAS) - change to sata or ide
In general system works great. It's not HIGH LOADED. It runs only a DB and HASP KEY.
DB Load is low.
CPU is mostly idle.
Memory was set to 2GB - enough.
Anyway to contact VMware support on this issue?
Thank you.
I hope we can fix this interesting error.
My log is attached, if you have any advice please write.