Deploying multiple virtual machines in VMware vCenter Server 5.x and 6.0.x from the same template fails with the error: vmdk access error

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• Deploying multiple virtual machines in VMware vCenter Server 5.x and 6.0.x from the same template fails
• You see the error:
  
  vmdk access error

• In the C:\ProgramData\VMware\VMware VirtualCenter\Logs\vpxd.log file, you see entries similar to:
  
  <YYYY-MM-DD>T<time>.937+01:00 [07788 info 'vpxdvpxdVmomi'] [ClientAdapterBase::InvokeOnSoap] Invoke done (9.128.135.212, vmodl.query.PropertyCollector.waitForUpdates)
  <YYYY-MM-DD>T<time>.938+01:00 [07280 error 'VmProv' opID=1037D47B-00000188-46-ef] Failed to track task vim.Task:task-148698 on host vim.HostSystem:host-479: vim.fault.FileFault
  --> backtrace:
  --> backtrace[00] rip 000000018018aafa
  --> backtrace[01] rip 0000000180102568
  --> backtrace[02] rip 00000001801038de
  --> backtrace[03] rip 000000018008d24b
  --> backtrace[04] rip 0000000000af6991
  --> backtrace[05] rip 000000013fa772e4
  <YYYY-MM-DD>T<time>.938+01:00 [07280 error 'VmProv' opID=1037D47B-00000188-46-ef] Aborting task tracking since task vim.Task:task-148698 failed
  -->
  <YYYY-MM-DD>T<time>.938+01:00 [07280 error 'vpxdvpxdDatastore' opID=1037D47B-00000188-46-ef] [VpxdDatastore::UrlToDSPath] Received a non-url [/vmfs/volumes/4eba8ae3-e73bb054-472f-e61f13aaee0b/POT Worklight 6/POT Worklight 6.vmdk], instead of a url
  <YYYY-MM-DD>T<time>.938+01:00 [07280 error 'VmProv' opID=1037D47B-00000188-46-ef] [Workflow] Get exception while executing action vpx.vmprov.CopyVmFiles: vim.fault.FileFault
  </time></time></time></time></time>
  Note: For more information, see Location of vCenter Server log files (1021804).
  Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vCenter Server 6.0.x
VMware vCenter Server 5.1.x
VMware vCenter Server 5.5.x
VMware vCenter Server 5.0.x

Cause

This issue occurs because the -ctk.vmdk file is locked exclusively by vpxa during the cloning process when multiple ESXi hosts are deploying virtual machines from the same template.

Resolution

This is a known issue affecting VMware vCenter Server 5.x and 6.0.x.

This issue is resolved in VMware ESXi 5.0, Patch Release ESXi500-201412001, available at VMware Downloads. For more information, see VMware ESXi 5.0, Patch Release ESXi500-201412001 (2088715).

Currently, there is no resolution for ESXi 5.1, 5.5, and 6.0.

To work around this issue, delete any -ctk.vmdk files associated with the virtual machine template. After completion, disable Change Block Tracking (CBT).

To delete any -ctk.vmdk files associated with the virtual machine template:

1. Log in to the VMware vCenter Server with administrator credentials either through the vSphere Client or the vSphere Web Client.
2. Browse the VMFS datastore where the affected virtual machine template is located.
3. Move or delete any of the associated -ctk.vmdk files from the VMFS datastore.

To disable Change Block Tracking (CBT):

1. Power off the virtual machine.
2. Right-click the virtual machine and click Edit Settings.
3. Click the Options tab.
4. Click General under the Advanced section and then click Configuration Parameters. The Configuration Parameters dialog opens.
5. Set the ctkEnabled parameter to false for the corresponding SCSI disk.

Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box. Changed Block Tracking (CBT) on virtual machines
Enabling or disabling Changed Block Tracking (CBT) on virtual machines
VMware ESXi 5.0, Patch Release ESXi500-201412001
同じテンプレートから複数の仮想マシンを VMware vCenter Server 5.x および 6.0.x でデプロイしようとすると、次のエラーで失敗する：vmdk アクセス エラー
通过同一个模板在 VMware vCenter Server 5.x 和 6.0.x 中部署多个虚拟机失败并显示“vmdk 访问错误”错误