I have Vmware Server RC1 running on a windows 2003 SP1 host with 2 VMs.
The host is running on a RAID 5 setup with 3x 146 15K SCSi hard drives and I've noticed that the average disk queue length (in performance manager) when running the two VMs are spiking to 100% every 5 seconds (pretty regular intervals). Paging and Processor time are normal.
The guest Vms are allocated 2Gb and 1 GM ram (the host has 4GB) and they have plenty of ram in reserve when I checked in the VMs.
The Host is a dual xeon 3.2Ghz HP DL380 G4 and disk space is preallocated in 2GB chunks.
One of the VMs run a mail server and the other a backup DC. I've update the drivers and ROM on the smart array controller but this has no impact on the host. I've checked the array and host system logs but no problems there.
I have noticed in the vmlog, there are these entries:
Jun 25 14:04:56: vmx| SCSI0:0: Command WRITE(10) took 1.790 seconds (ok)
Jun 25 14:04:56: vmx| SCSI0:0: Command WRITE(10) took 1.780 seconds (ok)
Jun 25 14:04:56: vmx| SCSI0:0: Command WRITE(10) took 1.783 seconds (ok)
Jun 25 14:04:56: vmx| SCSI0:0: Command WRITE(10) took 1.478 seconds (ok)
Jun 25 14:04:56: vmx| SCSI0:0: Command WRITE(10) took 1.837 seconds (ok)
Jun 25 14:05:55: vmx| SCSI0:0: Command WRITE(10) took 1.384 seconds (ok)
Jun 25 14:06:36: vmx| SCSI0:0: Command WRITE(10) took 1.434 seconds (ok)
Jun 25 14:07:28: vmx| SCSI0:0: Command WRITE(10) took 1.202 seconds (ok)
Jun 25 14:07:29: vmx| SCSI0:0: Command WRITE(10) took 1.036 seconds (ok)
Jun 25 14:07:44: vmx| SCSI0:0: Command WRITE(10) took 1.410 seconds (ok)
Jun 25 14:07:56: vmx| SCSI0:0: Command WRITE(10) took 1.462 seconds (ok)
Jun 25 14:08:10: vmx| SCSI0:0: Command WRITE(10) took 1.544 seconds (ok)
Jun 25 14:08:21: vmx| SCSI0:0: Command WRITE(10) took 1.094 seconds (ok)
Jun 25 14:08:21: vmx| SCSI0:0: Command WRITE(10) took 1.162 seconds (ok)
Jun 25 14:08:21: vmx| SCSI0:0: Command WRITE(10) took 1.076 seconds (ok)
Jun 25 14:08:21: vmx| SCSI0:0: Command WRITE(10) took 1.105 seconds (ok)
Jun 25 14:08:21: vmx| SCSI0:0: Command WRITE(10) took 1.285 seconds (ok)
Jun 25 14:08:21: vmx| SCSI0:0: Command WRITE(10) took 1.314 seconds (ok)
Jun 25 14:08:21: vmx| SCSI0:0: Command WRITE(10) took 1.269 seconds (ok)
Jun 25 14:08:22: vmx| SCSI0:0: Command WRITE(10) took 1.443 seconds (ok)
Jun 25 14:08:22: vmx| SCSI0:0: Command WRITE(10) took 1.111 seconds (ok)
Jun 25 14:08:22: vmx| SCSI0:0: Command WRITE(10) took 1.226 seconds (ok)
Jun 25 14:08:34: vmx| SCSI0:0: Command WRITE(10) took 1.059 seconds (ok)
Jun 25 14:08:47: vcpu-1| TOOLS unified loop capability requested by 'toolbox-dnd'; now sending options via TCLO
Jun 25 14:08:47: vcpu-1| GuestRpc: Channel 2, registration number 1, guest application toolbox-dnd.
Jun 25 14:08:47: vcpu-1| DISKUTIL: scsi0:0 : toolsVersion = 6529
Jun 25 14:08:54: vmx| SCSI0:0: Command READ(10) took 1.275 seconds (ok)
Jun 25 14:08:54: vmx| SCSI0:0: Command WRITE(10) took 1.302 seconds (ok)
Jun 25 14:08:54: vmx| SCSI0:0: Command WRITE(10) took 1.321 seconds (ok)
Jun 25 14:08:54: vmx| SCSI0:0: Command WRITE(10) took 1.333 seconds (ok)
Jun 25 14:09:05: vmx| SCSI0:0: Command WRITE(10) took 1.380 seconds (ok)
Jun 25 14:09:06: vmx| SCSI0:0: Command WRITE(10) took 1.439 seconds (ok)
Jun 25 14:09:49: vcpu-1| GuestRpc: Channel 2 reinitialized.
Jun 25 14:10:34: vmx| SCSI0:0: Command WRITE(10) took 1.347 seconds (ok)
Jun 25 14:10:34: vmx| SCSI0:0: Command WRITE(10) took 1.362 seconds (ok)
Jun 25 14:10:35: vmx| SCSI0:0: Command WRITE(10) took 1.877 seconds (ok)
Jun 25 14:10:35: vmx| SCSI0:0: Command WRITE(10) took 1.849 seconds (ok)
Jun 25 14:10:35: vmx| SCSI0:0: Command WRITE(10) took 1.673 seconds (ok)
Jun 25 14:10:35: vmx| SCSI0:0: Command WRITE(10) took 1.855 seconds (ok)
Jun 25 14:10:35: vmx| SCSI0:0: Command WRITE(10) took 1.863 seconds (ok)
Jun 25 14:10:35: vmx| SCSI0:0: Command WRITE(10) took 1.875 seconds (ok)
Jun 25 14:10:35: vmx| SCSI0:0: Command WRITE(10) took 1.892 seconds (ok)
Debugging is turned off as well.
Anyone ever ran into this problem before? Any suggestions I could take to fix this?
Message was edited by:
MotionS
Message was edited by:
MotionS
Message was edited by:
MotionS