I opened one of my VM's - i had obviously moved the vm it was linked to - and when it asked me to browse - I browsed to the wrong VM
Now I'm stuck as its pointing at the wrong one - where can I repoint back at the correct linked vm
This is not a easy task and you would better off copying it again.
Try editing the clone's .vmx file in a text editor and changing the "fileSearchPath" line to use the correct path to the parent VM.
>> Try editing the clone's .vmx file in a text editor and changing the "fileSearchPath" line to use the correct path to the parent VM.
Eventually that may corrupt the master.
I'd first copy the master VM back in to its original place and then point to the new copy of the master.
This will prevent a destruction of the master - if this VM suffers from the absolute-path-bug.
How can a linked clone corrupt its parent VM? The parent VM should never be touched, even with absolute paths...
One delete-snapshot or revert-to can do that very easily.
In unlucky constellations even one start of the copy may make the master unusable.
Do you want link to examples for this ?
Yes, please. I can see how powering on the clone could corrupt the clone if it's not parented correctly, but I still am not sure how the base VM's disks could be altered. The parent disks always should be immutable...
