Symptoms
Storage vMotion fails with error similar to:
An error occurred while communicating with the remote host. Migrating Virtual Machine active state
In the vmware.log file, you see the entries similar to:
017-01-12T17:42:19.530Z| Worker#1| I120: SVMotion: Enter Phase 8
2017-01-12T17:42:19.629Z| Worker#1| I120: Disk/File copy started for /vmfs/volumes/528a4a82-403b36a8-5cf2-1cc1de1cf19c/CRSecVid_VM/CRSecVid_VM.vmdk.
2017-01-12T17:42:19.740Z| vcpu-0| I120: HBACommon: First write on scsi0:0.fileName='/vmfs/volumes/5846c857-a538dc2c-39c4-9cb65488f208/CRSecVid_VM/CRSecVid_VM_2.vmdk'
2017-01-12T17:42:19.741Z| vcpu-0| I120: DDB: "longContentID" = "0f27513e4da5cb398a7113f47fdc3ae2" (was "113f5adc309c13dacc7cd37a014e577b")
2017-01-12T17:42:19.844Z| vcpu-0| I120: DISKLIB-CHAIN : DiskChainUpdateContentID: old=0x14e577b, new=0x7fdc3ae2 (0f27513e4da5cb398a7113f47fdc3ae2)
2017-01-12T17:42:19.850Z| vcpu-2| I120: HBACommon: First write on scsi0:1.fileName='/vmfs/volumes/528a4a82-403b36a8-5cf2-1cc1de1cf19c/CRSecVid_VM/CRSecVid_VM.vmdk'
2017-01-12T17:42:19.850Z| vcpu-2| I120: DDB: "longContentID" = "c40278c7604e41bbe80a96888f37e2b0" (was "a234a3887bbf3f9ea4ff5c063f051ad2")
2017-01-12T17:42:19.913Z| vcpu-2| I120: DISKLIB-CHAIN : DiskChainUpdateContentID: old=0x3f051ad2, new=0x8f37e2b0 (c40278c7604e41bbe80a96888f37e2b0)
2017-01-12T18:25:51.039Z| vmx| I120: Migrate: Cancel requested.
In the /var/log/vmkernel.log file, you see the entries similar to:
2017-01-12T18:11:13.313Z cpu11:33524)ScsiDeviceIO: 2651: Cmd(0x439e01216200) 0x83, CmdSN 0x782e77 from world 4095701 to dev "naa.60014380063c470100028000008e0000" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0xa 0xd 0x1.
2017-01-12T18:11:13.314Z cpu11:33524)ScsiDeviceIO: 2651: Cmd(0x439e0127bd00) 0x83, CmdSN 0x782e78 from world 4095701 to dev "naa.60014380063c470100028000008e0000" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0xa 0xd 0x1.
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
Cause
ESXi host is enabled with the XCOPY. This issue occurs because of the device failure at the storage end.
Resolution
To resolve this issue, contact the storage vendor and resolve the device failure issue.
Workaround
To workaround this issue, disable the XCOPY:
esxcli system settings advanced set --int-value 0 --option /DataMover/HardwareAcceleratedMove
