The two VM's I have keep crashing....with the following messages in the Event logs.
Can someone guide me to track down what could be causing this? One of the messages talks about the resick.timeout parameter setting, but does not recommend changing it. The other one talks about a bug # 41568.
Thanks
07/06/09 11:45:09 AMSeverity:InformationTask:Not applicableTask ID:Not applicableObject:RacbTriggered By:UserDescription:Message
from i7ubuntu: VMware Server unrecoverable error: (vmx)
NOT_IMPLEMENTED
/build/mts/release/bora-156745/bora/devices/scsi/scsiDisk.c:2849
bugNr=41568
A log file is available in "/u02/VM/Racb/vmware.log". Please request
support and include the contents of the log file. 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.
We will respond on the basis of your support entitlement.
Message
from i7ubuntu: This virtual machine has been unresponsive for more than
20 seconds and has caused another virtual machine sharing a disk with
it via SCSI reservations to believe it has died. It is therefore unsafe
for this virtual machine to resume activity, and this virtual machine
will now terminate. If a 20 second delay is not long enough to be an
accurate 'death heuristic' it can be changed by setting the
"reslck.timeout" configuration variable. It is extremely unlikely that
this should ever be necessary.
From the vmware-0.log I do see some of the writes taking a long time on one of the shared disks, and when that write exceeds 20 secs it seems to core dump. No idea why it's taking that long to write to those disks.
Jul 05 02:24:05.008: vmx| DISK: Resync'ing disk scsi1:5.
Jul 05 02:24:05.823: vmx| DISKLIB-DSCPTR: Opened : "asm3.vmdk" (0x6a)
Jul 05 02:24:05.823: vmx| DISKLIB-LINK : Opened '/u02/VM/shared/asm3.vmdk' (0x6a): monolithicSparse, 20971520 sectors / 10 GB.
Jul 05 02:24:05.823: vmx| DISKLIB-LIB : Opened "/u02/VM/shared/asm3.vmdk" (flags 0x6a).
Jul 05 02:24:05.831: vmx| scsi0:0: Command WRITE(10) took 10.838 seconds (ok)
Jul 05 02:24:05.832: vmx| scsi1:5: Command READ(10) took 17.914 seconds (ok)
Jul 05 02:24:05.832: vmx| scsi1:5: Command READ(10) took 15.631 seconds (ok)
Jul 05 02:24:05.832: vmx| scsi1:5: Command READ(10) took 17.857 seconds (ok)
Jul 05 02:24:09.078: vmx| SCSI DISK RESERVATION: Pid 4577 has forcibly preempted a write lock (previous: c0025965, new: 80025966)
Jul 05 02:24:09.078: vmx| DISK: Resync'ing disk scsi1:2.
Jul 05 02:24:12.888: vmx| DISKLIB-DSCPTR: Opened : "votingdisk.vmdk" (0x6a)
Jul 05 02:24:12.888: vmx| DISKLIB-LINK : Opened '/u02/VM/shared/votingdisk.vmdk' (0x6a): monolithicSparse, 20971520 sectors / 10 GB.
Jul 05 02:24:12.888: vmx| DISKLIB-LIB : Opened "/u02/VM/shared/votingdisk.vmdk" (flags 0x6a).
Jul 05 02:24:12.898: vmx| SCSI DISK RESERVATION: Pid 4577 has forcibly preempted a write lock (previous: c0025966, new: 80025967)
Jul 05 02:24:12.898: vmx| scsi1:5: Command WRITE(10) took 5.790 seconds (ok)
Jul 05 02:24:12.899: vmx| scsi0:0: Command WRITE(10) took 4.049 seconds (ok)
Jul 05 02:24:12.899: vmx| scsi0:0: Command WRITE(10) took 4.049 seconds (ok)
Jul 05 02:24:12.906: vmx| Msg_Post: Error
Jul 05 02:24:12.906: vmx| http://msg.scsi.reservation.locktimeoutrecover This virtual machine has been unresponsive for more than 20 seconds and has caused another virtual machine sharing a disk with it via SCSI reservations to believe it has died. It is therefore unsafe for this virtual machine to resume activity, and this virtual machine will now terminate. If a 20 second delay is not long enough to be an accurate 'death heuristic' it can be changed by setting the "reslck.timeout" configuration variable. It is extremely unlikely that this should ever be necessary.
Jul 05 02:24:12.906: vmx| -
Jul 05 02:24:12.908: vmx| SCSI DISK: key0=153959 key1=153958
Jul 05 02:24:12.908: vmx| NOT_IMPLEMENTED /build/mts/release/bora-156745/bora/devices/scsi/scsiDisk.c:2849 bugNr=41568
Jul 05 02:24:12.909: vmx| Core dump limit is 0 KB.
Jul 05 02:24:13.910: vmx| Child process 21225 failed to dump core (status 0x6).
Jul 05 02:24:13.910: vmx| Backtrace: