Nowadays some customers deploy Microsoft Clustering virtual machine on VMware vSphere, but they encountered one problem on Microsoft Clustering virtual machine, ie it cannot execute vMotion when the virutal machine in power on status. Because Microsoft Clustering is required the shared disks between each cluster node, ie each virtual machine needs to access the share disks in RDM format on VMware vSphere. Prior to vSphere 5.5, if the virtual machine its virtual disk (RDM) is shared bettwen the virtual machines, it can only execute vMotion when the virtual machine power down. In vSphere 6.0, it doesn’t have this limitaion. We can online migrate the virtual machine between the ESXi host by vMotion if its virtual disk (RDM) is shared bettwen the virtual machines. The following is demonstration in my lab environment.
VM: TestVM and TestVM2, its operating system is Microsoft Windows 2008 R2. There are one RDM is shared between TestVM & TestVM2.
VMware vSphere: VMware vSphere 6.0 U2, 10.2.1.8 and 10.2.1.9
VMware vCenter 6.0 U2
NOTE: The hardware version of each virtual machine needs to upgrade veresion 11. It cannot execute vMotion bettween ESXi host if its hardware version is prior to version 11.
If its hardware version of each virtual machine is 11, it can execute vMtoion bettween ESXi host.
Finally the TestVM can migrate into standby ESXi host by vMotion.