Cancelling a storage vMotion task causes a VM to crash
Article ID: 318198
Updated On:
Products
VMware vCenter Server
Issue/Introduction
Symptoms:
A storage vMotion task involving individual disks (not the primary directory where the VMX resides) on a VM is cancelled. After the cancellation of the storage vMotion task you experience:
- Loss of access to the VM
- The VM directory will have a new vmx-zdump file present
Environment
VMware vCenter Server 7.0.x
Cause
This is due to how the cancellation for a storage vMotion is handled on the backend with individual disks for a VM compared to how storage vMotion is handled for an entire VM migration.
Resolution
This issue is resolved in vSphere ESXi 7.0 U3i (build number 20842708).
Workaround:
Do not cancel storage vMotion task if you do not want the VM to crash when migrating individual disks. Please let the storage vMotion task finish and then migrate the VM back to the originating storage or different storage.
Workaround:
Do not cancel storage vMotion task if you do not want the VM to crash when migrating individual disks. Please let the storage vMotion task finish and then migrate the VM back to the originating storage or different storage.
Additional Information
Impact/Risks:
This issue only occurs at ESXi7.0U3 and later.
This issue only occurs at ESXi7.0U3 and later.
Feedback
Yes
No
Powered by
