ESXi host 6.0 and 6.5 fails with PSOD (purple screen of death) - "SCSI_DeviceClusteringClearState" when vMotion occurs for a MSCS VM.
search cancel

ESXi host 6.0 and 6.5 fails with PSOD (purple screen of death) - "SCSI_DeviceClusteringClearState" when vMotion occurs for a MSCS VM.

book

Article ID: 317546

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • ESXi 6.0 and 6.5 host fails with a PSOD (purple screen of death) -  "SCSI_DeviceClusteringClearState" when vMotion occurs for a MSCS VM.
  • You see the backtrace similar to:
Backtrace for current CPU ###, worldID=######, fp=0x####
0#####:[0#####]SCSI_DeviceClusteringClearState@vmkernel#
0#####:[0#####]VSCSI_DestroyDevice@vmkernel#
0#####:[0#####]UW64VMKSyscallUnpackVSCSIDestroyDev@(user)#
0#####:[0#####]User_UWVMK64SyscallHandler@(user)#
0#####:[0#####]SyscallUWVMK64@vmkernel#nover
0#####:[0#####]gate_entry_@vmkernel#nover
  • 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.


Cause

  • 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

Resolution

This issue is resolved in:
VMware ESXi 6.5, Patch Release ESXi650-201811002. 
VMware ESXi 6.0, Patch Release ESXi600-201909001. 


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: