Symptoms:

• ESXi 6.0 and 6.5 host fails with a PSOD -  "SCSI_DeviceClusteringClearState" when vMotion occurs for a MSCS VM.
• You see the backtrace similar to:

• Clustering node virtual machines contain shared non-RDM disk (VMDK or VVOL).
• Clustering node Virtual Machines are in a CAB (Cluster Across Box) configuration.
• SCSI Bus Sharing mode is set to Physical.

• This issue occurs due to misconfiguration of non-RDM disks across the hosts in physical bus sharing mode during vMotion of MSCS virtual machines. This issue may also occur during vMotion of VVOLs
• PSOD can occur for Oracle RAC VMs too when they are vMotioned

This issue is resolved in:
VMware ESXi 6.5, Patch Release ESXi650-201811002. For more information, see https://docs.vmware.com/en/VMware-vSphere/6.5/rn/esxi650-201811002.html.

VMware ESXi 6.0, Patch Release ESXi600-201909001. For more information, see https://docs.vmware.com/en/VMware-vSphere/6.0/rn/esxi600-201909001.html.


Workaround:
To work around this issue, setup the virtual machines cluster by using the following shared storage configuration for MSCS in vSphere:

Note: You must use one of these configuration to setup virtual machines.

• Microsoft Cluster on a Single Host with one or more shared eagerzeroedthick virtual disks.
• Microsoft Cluster on a Single Host with one or more shared RDMs in Virtual Compatibility mode.
• Microsoft Cluster across Hosts with one or more shared RDMs in Physical Compatibility mode.

Note: All these configurations involves sharing of RDMs/VMDKs. Relevant virtual machine Affinity or Anti-affinity rules must be configured to disallow unnecessary virtual machines migration.

For more information, see:

• Setup for Failover Clustering and Microsoft Cluster Service Guide
• Microsoft Cluster Service (MSCS) support on ESXi/ESX (1004617)
• Microsoft Windows Server Failover Clustering on VMware vSphere 6.x: Guidelines for supported configurations (2147661)

Refer to VMware KB : How to Download ESXi, vCenter Server Patches in Customer Connect