book
Article ID: 311220
calendar_today
Updated On:
Environment
VMware vSphere ESXi 5.0
VMware ESXi 4.0.x Embedded
VMware ESXi 4.0.x Installable
VMware ESXi 4.1.x Installable
VMware vSphere ESXi 5.5
VMware ESXi 4.1.x Embedded
VMware vSphere ESXi 5.1
Cause
This issue occurs if VAAI is enabled on the ESXi host, and the connected storage array does not execute VAAI commands correctly or successfully. This can be caused by out-of-date firmware on the storage array, or an unsupported make and model of array. The indicated SCSI return code shows an XCOPY command failed due to a Bus Busy condition. If the storage array did not support VAAI, the host would not have tried to use the XCOPY command, so the command itself failed when it should have succeded.
Note: When a storage connection splitter is used, the splitter itself may fail to recognize VAAI commands or deal with them correctly.
Resolution
The correct resolution of this issue is to engage the storage vendor and have them investigate the XCOPY failures and resolve them. This may require a maintenance window if the array needs to be rebooted.
The accepted temporary workaround for this issue is to disable VAAI on the ESXi host while performing a Storage vMotion migration.
Additional Information
To be alerted when this document is updated, click the Subscribe to Article link in the Actions box
Disabling the VAAI functionality in ESXi/ESXVMware Storage vMotion が進捗21%の時点で次のエラーで失敗する:Storage VMotion failed to copy one or more of the VM's disks Impact/Risks:
This error will affect both manual and SDRS storage vmotions; both will fail similarly. In general the use of VAAI operations yield large performance increases for certain operations which otherwise would be time-consuming. Turning off VAAI will cause performance loss in a healthy environment.