Thanks for your response

i was able to migrate(Vmotion) the master VM from one ESX(say host1) host to the other ESX Server(say host2) but when i tried to migrate the LInked clone VM from host1 to host2, i was prompted with the following error :

"Moving a virtual machine that ha snapshot is not supported when the virtual machine has disks placed outside of its home datastore"

So later i tried the alternative option: tar the Linked VM file which has the files(e.g *flat.vmdk , *.vmdk , *.vmx etc) and copied the tar file to other ESX Server. Untarred the Linked VM and tried adding the Linked Clone VM to ESx Server. i was successful in adding the Linked Clone VM to the inventory. I had also migrated the parent VM to the other ESX host. But when i tried to power on the Linked Clone VM i was again prompted with another error:

"File not found"

So when i checked the *.vmdk file of Linked Clone VM it was still pointing to host1 datastore /vmfs/volumes/host1:storage1 so i changed the datastore as vmfs/volumes/host2-storage1 and powerer on the VM and again prompted with another error:

"a general system error occured:internal error"

Please let me know where i m going wrong as i am not able to power on the Linked Clone VM. And what are file i suppose to modify in the Linked Clone VM as well as in parent VM so that it should resolve my problem.

Regards

Pardeep Singh

Thanks for your response

Can you pls tell me where can i look for "fileSearchPath" points and which files has fileSerachPath.

Regards

Pardeep Singh

Thanks for yuor response.

I had already explained in my prevoius mail that i m not able to power on the Linked Clone VM after migrating(tar method used to migrate) though the parent VM is also present in the ESX Server.

Today i noticed one thing , I found while registering the Linked Clone VM in ESx Server, the Linked Clone VM does not have any snapshot of parent VM in the "snapshot Manager" of VI Client. Actually speaking the Linked Clone VM should have the parent VM snapshot after registering the VM. So i think this could be the reason that i am not able to power on the Linked Clone VM. But usually when we register any VM which has snapshot also contain the snapshot in the "snapshot manager". But I am not sure for Linked Clone VM in ESX 3.x why the VM does not have the snapshot in the "snapshot manager" of VI Client though the snapshot is present in the file.

So could u pls tell me the way to add the snapshot back to the Linked Clone VM so that Linked Clone VM should be pointing to parent VM snapshot.

Regards

Pardeep Singh

Now I am able to power on the Linked Clone VM after migrating to other ESX host. Let me explain you the steps i followed to resolve the issue after untarring the Linked Clone VM:

1. Change the contents of LinkedClone-2.vmsd file present under /vmfs/volumes/storage-name/Linked-Clone-2/ from

snapshot0.disk0.fileName = "/vmfs/volumes/ host1:storage1/MASTER-LinkedClone-1/MASTER-LinkedClone-1.vmdk"

to

snapshot0.disk0.fileName = "/vmfs/volumes/host2-storage1/MASTER-LinkedClone-1/MASTER-LinkedClone-1.vmdk"

The above step is to make sure to add the snapshot back to the Linked Clone VM after Untarring the Linked Clone VM file.

2 Select the "Revert to snapshot" option in the VI Client and power on the VM.

Regards

Pardeep Singh