Inconsistent Windows virtual machine performance when disks are located on SAN datastores (1014)
- Bluescreen errors
- Event ID: 9 messages in the Event Viewer
- This error reported in guest operating system:
The device, \Device\ScsiPort0, did not respond within the timeout period
- Virtual machine becomes unresponsive, halts, or is inaccessible from the console
Windows guest operating systems that are using virtual disks on non-local datastores might experience unexpected blue screens.
This issue occurs when the responses from the storage array take longer than the guest operating system expects to wait. The default disk timeout period in Windows is too short to handle the longer delays that can occur in a SAN, NFS, or iSCSI environment, and a blue screen error is the result of exceeding this timeout.
- In the registry, go to HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Disk.
- Right-click and select Edit/Add value.
- Set the value name to TimeOutValue.
- Set the data type to REG_DWORD.
- Set the data to 0x03c hex (or 60 decimal).
- Reboot the virtual machine.
- Contact your Storage vendor to confirm whether a specific TimeOutValue setting has been identified for your particular environment.
- Increasing this disk timeout setting does not affect the performance of the guest operating system or virtual machine under normal operating conditions, but you must verify how the applications you are running in the guest operating system handle disk access delays.
- To accommodate transient events, VMware Tools increases the SCSI disk timeout to 60 seconds for Virtual Infrastructure 3 and 180 seconds for vSphere 4 and later.