OPERATIONAL DEFECT DATABASE
...
...
Cannot migrate a virtual machine using Storage vMotion Storage migration of a virtual machine fails You see this error:A general system error occurred: Storage vMotion failed to copy one or more of the VM's disks. Please consult the VM's log for more details, looking for lines starting with "CBTMotion". In the logs of the affected virtual machine, you see entries similar to these:Nov 12 18:15:01.079: Worker#0| CBTMotion: scsi0:1: Clone: failed to start block tracking session on source disk: Change tracking is not active for this disk.Nov 12 18:15:01.080: Worker#0| CBTMotion: scsi0:1: failed to clone disk from /vmfs/volumes/UUID/vmname.vmdk to /vmfs/volumes/UUID/vmname.vmdk.Nov 12 18:15:01.080: Worker#0| CBTMotion: disk clone failed, aborting Storage VMotion.Nov 12 18:15:01.080: Worker#0| Msg_Post: ErrorNov 12 18:15:01.080: Worker#0| [msg.cbtmotion.disk.clone.failed] Disk clone failed. Canceling Storage vMotion.
To resolve this issue, create a snapshot of the affected virtual machine and then commit the snapshot. To create and commit the snapshot: In the vSphere Client, right-click the virtual machine. Click Snapshot > Take Snapshot. In the vSphere Client right-click the virtual machine. Click Snapshot > Snapshot Manager. Select the snapshot you created in Step 1. Click Delete.
Storage vMotion が次のエラーで失敗する： Storage vMotion で仮想マシンのディスクを 1 つ以上コピーできませんでした
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
