VM cloning to different datastore

[MariuszII]

Hi all,

I copied a VM from NetApp based datastore to local datastore (via Datastore browser in the vSphere web client). Source & destination ESXi Hosts have the same version 6.5.0.

ESX source system-> version 6.5.0 Build 4564106

ESX destination system-> version 6.5.0 Build 6765664

After the files have been transferred I registered the VM on the destination ESXi Host via VMWare Webclient and tried to start the VM some errors (several records with the same error message) occured:

"File system specific implementation of LookupAndOpen{file} failed
Cannot open the disk .... or one of the snapshot disks it depends on

Module "Disk" power on failed"

I also detected that my vDisks (originally "thin provisioned" ) apear now as "thick provisioned" on the destination ESXi host.

The VM doesn't start.

Can I fix this problem? Do you have some ideas?

[msripada]

Can you check if the scratch is configured on the same location where the VM is trying to power on on the destination?

Similar to this kb

VMware Knowledge Base

thanks,

MS

[johnnyknoxville]

Does your "original" VM have some Snapshot?

[admin]

Depending on the storage, there may not be a lock file.

The vmkfstools -D command is the most useful for determining the source MAC address.

Regards,

Randhir

[Finikiez]

Can you repro the issue (try to power on VM), collect and attach the following logs after that: vmware.log of the affected VM and vmkernel.log from ESXi host where it's regestered.

vmware.log is located in VM's directory on datastore

vmkernel.log is located in /var/log directory on ESXi host