Hi Martin, Thanks for sharing the wonderful feature and it works great, i have a question, when i run the hostcustomisation.sh script on the source VM, it freezes and when i run the deploy script it instantly clones the VMs perfectly, once the VMs are cloned, the source VM always remains in the freezing state it did not come to normal, is this the behaviour expected ? Could you please let me know.
When creating instant clones, a new delta disk version is created on the source VM each time. These delta files are not removed when you remove the instant clone VM or when you do a disk consolidation. Do you know how to clean these files up?
There is no way how to alter the Clones if you make a change to the Parent. Actually, there are two scenarios: 1) Parent VM is freezed In this situation, the Clones will all start from the same state 2) Parent VM is running In this situation, the Clones will be at the exact same state as the Parent when the Instant Clone was invoked (i.e. First set of Clones will start from "state1" and after several hours you will create new set of Clones - but those will be running from "state2" of the Parent)
This is really very very helpful. Works perfectly for me. Thanks for sharing.
how about deploying Windows VMs the same way?
Hi Martin, Thanks for sharing the wonderful feature and it works great, i have a question, when i run the hostcustomisation.sh script on the source VM, it freezes and when i run the deploy script it instantly clones the VMs perfectly, once the VMs are cloned, the source VM always remains in the freezing state it did not come to normal, is this the behaviour expected ? Could you please let me know.
When creating instant clones, a new delta disk version is created on the source VM each time. These delta files are not removed when you remove the instant clone VM or when you do a disk consolidation. Do you know how to clean these files up?
What if I make changes to the master after deploying an instant clone, is there a way to push those changes to the clones?
There is no way how to alter the Clones if you make a change to the Parent.
Actually, there are two scenarios:
1) Parent VM is freezed
In this situation, the Clones will all start from the same state
2) Parent VM is running
In this situation, the Clones will be at the exact same state as the Parent when the Instant Clone was invoked (i.e. First set of Clones will start from "state1" and after several hours you will create new set of Clones - but those will be running from "state2" of the Parent)
Awesome. Thanks
how about deploying Windows VMs the same way?