Deployed or cloned VM base disk points to template

I have heard that we are getting a few calls into support on this one, so I am rushing this new Knowledgebase article ( https://kb.vmware.com/kb/1007755 to be publicly available. It’s not quite out yet, so here’s the scoop.

  • Deployed VM’s base disk will point to the original template’s vmdk if Edit Virtual Hardware is used to modify it.
  • A cloned VM’s base disk will point to the original VM’s vmdk if Edit Virtual Hardware is used to modify it.

The problem is caused by a bug in hostd. When reconfiguring of the vmdk happens, hostd sets the vmdk path in the vmx to the backing disk in the config specification.

VMware is aware of the problem and expects a future release to address it. The current recommendation is to not use this (currently experimental) feature.

In the case that you already used the feature:

  1. After deploying the VM, review the VM properties, specifically the virtual disk location.
  2. Change the virtual disk settings manually to point to the correct file by right-clicking the VM and selecting Edit Settings…
  3. In the Hardware tab, select Hard Disk 1
  4. Verify the Disk File box points to the intended vmdk file.  If it does not remove the Hard Disk.
  5. Click Add… and use the Hardware Wizard to select the correct vmdk file.

3 thoughts on “Deployed or cloned VM base disk points to template”

  1. I believe I’ve experienced this bug ever since upgrading to ESX 3.5 and I know I opened a support case about it before. I’m surprised they’re just addressing it now.

Comments are closed.