VM deployed via template still referencing template .vmdk file

[Gordow]

While attempting to create a new VM today from our template, I discovered that the last VM I created from the template still is referencing the templates .vmdk file instead of it's own. If I view the .vmx file for the VM, I see the following lines:

scsi0:0.fileName = "/vmfs/volumes/4890120e-1ada0f0e-0523-001a6436eafe/COE_SERVER/COE_SERVER.vmdk"

This is incorrect. The problem I have now is that this incorrect reference for the VM has caused all the installed application and configuration information into the templates disk file instead of the correct one it's own VM location on the datastore.

How do I copy the templates .vmdk to the VM's folder in the datastore and then rename it to match the VM's name? I can copy the file via VirtualCentre but it won't allow me to rename the file, even if I removed the VM from the inventory. What's the best way to edit the .vmx file to correct the .vmdk reference?

Thanks in advance!

[dm330]

If you used the expiremtal feauture from deploying a vm from a template and editing the hardware before deployment you can have the scsi0 first disk point to the template disk

This is a known issue !

take a look at:

Knowledgebase article ( 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.

[tidup]

Hello,

Can I follow this issue if my VM is created since 6 months ?

Best Regards,

Gregory Duperron

[PhillyDubs]

Gregory,

This is a bug. Please update to 5.1 Update 1 where the issue is resolved and there should be no more concern about the template disk being used incorrectly.

[tidup]

Thanks but, my ESXi are in 4.1.0 702213 and my VirtualCenterServer are in 5.0.0 623373