VMware Cloud Community
billrich
Contributor
Contributor

Get "missing vmsn file" with linked clones

After upgrading ESXi and vCenter to 6.7, I've been getting the error "missing vmsn file" when I'm creating linked clones, but only from templates that were created after the upgrade. Templates created while running 6.5 still work fine. To test this, I downloaded the vmtx, vmsn, and vmsd files from an existing template and created a linked clone using that template. This worked fine. Then I converted the template to a VM, then immediately back to a template (without changing anything else). Then I downloaded the vmtx, vmsn, and vmsd files again, and attempted the linked clone. This time it failed. I diffed all the files and there are no changes. If I convert the template back to a VM, I am able to create the linked clone fine also. It seems to ONLY be VM templates that were converted to templates after upgrading to 6.7. I'm looking for any insight into what is happening here.

Tags (2)
2 Replies
rbeam
Contributor
Contributor

(Smells like a bug. Using 6.7.0U1, the layout changes between the two.  [ /mob/?moid=vm-72&doPath=layout ]

As a VM :

configFilestring[]
"New Virtual Machine Template.vmsd"
diskVirtualMachineFileLayoutDiskLayout[]
disk[2000]VirtualMachineFileLayoutDiskLayout
logFilestring[]Unset
snapshotVirtualMachineFileLayoutSnapshotLayout[]
snapshot["snapshot-73"]VirtualMachineFileLayoutSnapshotLayout
snapshot["snapshot-74"]VirtualMachineFileLayoutSnapshotLayout
snapshot["snapshot-87"]VirtualMachineFileLayoutSnapshotLayout
snapshot["snapshot-90"]VirtualMachineFileLayoutSnapshotLayout
swapFilestringUnset

As a template:

configFilestring[]
"New Virtual Machine Template.vmsd"
diskVirtualMachineFileLayoutDiskLayout[]
disk[2000]VirtualMachineFileLayoutDiskLayout
logFilestring[]Unset
snapshotVirtualMachineFileLayoutSnapshotLayout[]Unset
swapFilestringUnset

[Update: 6.5.0-9451637 does not clear the snapshot from layout]

sateeshc
Contributor
Contributor

I am also seeing same issue after upgrading to vCenter 6.7.

Not able to clone a template which was created from VM having 1 VM snapshot.

Reply
0 Kudos