[pve-devel] RFC: vm cloning implementation proposal

[Alexandre DERUMIER]

>>I do not understand why we need that? Please can you explain? 

with rbd,nexenta,sheepdog, it's mandatory to clone from a snapshot. (that's why the sourcevm don't need to be readonly after the clone, like qcow2)

# rbd clone <parentsnap> <clonename>
# collie vdi clone -s snapshot <src vdi> <dst vdi>
# zfs clone srcimage at snap1 cloneimage



>>After thinking more about that, I am quite sure that we do not want that. 
>>This will lead to many problem (for example duplicate MACs, ...). 
Oh yes, indeed, you are right.

----- Mail original ----- 

De: "Dietmar Maurer" <dietmar at proxmox.com> 
À: "Alexandre DERUMIER" <aderumier at odiso.com> 
Cc: pve-devel at pve.proxmox.com 
Envoyé: Mercredi 3 Octobre 2012 13:24:12 
Objet: RE: [pve-devel] RFC: vm cloning implementation proposal 

> >>You want to clone a specific snapshot? 
> Yes. we need to clone from a snapshot for sheepdog,rbd,nexenta. 
> So choosing the snapshot we want is good. 

I do not understand why we need that? Please can you explain? 

> >>Live cloning include VM state? 
> I don't think we need to clone the vmstate, But we can read the vmstate from 
> sourcevm for the first start of the cloned vm . ( we can't rollback on the clone 
> without a first snap) 

After thinking more about that, I am quite sure that we do not want that. 
This will lead to many problem (for example duplicate MACs, ...).