Migrating a virtual machine using vMotion fails after performing a disk-only Storage vMotion operation with change block tracking enabled
search cancel

Migrating a virtual machine using vMotion fails after performing a disk-only Storage vMotion operation with change block tracking enabled

book

Article ID: 328207

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:
  • vMotion of a virtual machine between hosts fail
  • In the vmware.log file, located in the virtual machine home directory, you see entries similar to:

    Worker#0| I120: DISKLIB-CTK : Change tracking file /vmfs/volumes/52530d26-7224e159dced-90e2ba14f1e8/ACMEVM/ACMEVM_1-ctk.vmdk is missing.
    Worker#0| I120: DISKLIB-CTK : Could not open change tracking file "/vmfs/volumes/52530d26-7224e159-dced-90e2ba14f1e8/ACMEVM/ACMEVM_1-ctk.vmdk": Change tracking invalid or disk in use.

  • In the vmware-##.log file, located at /vmfs/volumes/virtual_machine_datastore/ virtual_machine_folder/, you see entries similar to :

    <YYYY-MM-DD><time>| vmx| I120: [msg.literal] Could not open/create change tracking file</time>
    <YYYY-MM-DD><time>| vmx| I120: [msg.disk.noBackEnd] Cannot open the disk '/vmfs/volumes/533985f8-7e0a80a8-a6a2-2c59e53c7d08/DISK-NAME (7de1ff83-71a3-4b56-bbf3-afe5f195e7de)/DISK-NAME (7de1ff83-71a3-4b56-bbf3-afe5f195e7de).vmdk' or one of the snapshot disks it depends on.</time>
    <YYYY-MM-DD><time>| vmx| I120: [msg.moduletable.powerOnFailed] Module DiskEarly power on failed.</time>
    <YYYY-MM-DD><time>| vmx| I120: [msg.migrate.resume.fail] The VM failed to resume on the destination during early power on.</time>

  • Checking the output from the vmkfstools -D virtual_machine.vmdk command indicates DISK-NAME.ctk file(s) are locked as:

    <YYYY-MM-DD><time> cpu14:5280715)FS3: 198: <START <I>DISK-NAME (7de1ff83-71a3-4b56-bbf3-afe5f195e7de)-ctk.vmdk>
    </time>    <YYYY-MM-DD><time> cpu14:5280715)Lock [type 10c00001 offset 64182272 v 138, hb offset 3780608
    gen 31, mode 1, owner 5339cc31-e81a213c-3b52-2c59e53c49d8 mtime 8667775
    num 0 gblnum 0 gblgen 0 gblbrk 0]
    <FD c102 r91> is on Head Extent
    </time>    <YYYY-MM-DD><time> cpu14:5280715)Addr <4, 102, 91>, gen 137, links 1, type reg, flags 0x0, uid 0, gid 0, mode 600
    len 6554112, nb 7 tbz 0, cow 0, newSinceEpoch 7 zla 1, bs 1048576
    </time>    <YYYY-MM-DD><time> cpu14:5280715)FS3: 200: <END <I>DISK-NAME (7de1ff83-71a3-4b56-bbf3-afe5f</time>


Cause

This issue occurs only when you perform a Storage vMotion of the virtual machine's hard drive, while Change Block Tracking (CBT) is enabled and the virtual machine is powered on. The configuration files of the virtual machine remain in the original location. The virtual machine's Disk-Name.ctk files are left in a locked state which prevents future vMotion operations from succeeding.

Resolution

This issue is resolved in
ESXi 5.1 Update 2, available at VMware Downloads. For more information, see the VMware ESXi 5.1 Update 2 Release Notes.
ESXi 5.5 Update 2, available at VMware Downloads. For more information, see the VMware ESXi 5.5 Update 2 Release Notes.

This issue can be prevented by avoiding disk only Storage vMotion operations and moving virtual machine configuration data along with the disks.

To work around this issue, use one of these options:
  • Power off the virtual machine and Storage vMotion the affected drive again.
  • Set ctkEnabled and scsix:x.ctkEnabled parameter value to false.
To ctkEnabled and scsix:x.ctkEnabled parameter value to false:

Note: Ensure that you power off the virtual machine before performing these steps.
  1. Right-click the virtual machine and click Edit Settings.
  2. Click the Options tab.
  3. Click General under the Advanced section and click Configuration Parameters. The Configuration Parameters dialog opens.
  4. Set the ctkEnabled parameter value to false.
  5. Set the scsix:x.ctkEnabled parameter value to false.

    Note: scsix:x in scsix:x.ctkEnabled indicates the SCSI device assigned to the hard disk that is added to the virtual machine. Every hard disk added to the virtual machine is given a SCSI device that appears similar to scsi0:0, scsi0:1, or scsi 1:1.

  6. Power on the virtual machine and attempt the vMotion again.


Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box 変更ブロックのトラッキングが有効な状態でディスク オンリーの Storage vMotion 操作を実行した後に vMotion を使用して仮想マシンを移行すると失敗する
在启用更改块跟踪的情况下执行仅磁盘 Storage vMotion 操作后，使用 vMotion 迁移虚拟机失败

Powered by Wolken Software