[pve-devel] [PATCHV3 pve-container 4/4] Prevent that a CT run at cloning.

[Wolfgang]

First step include without running container.
Is this function in the code I want make it possible to clone if the
container is running.


2016-05-11 9:18 GMT+02:00 Fabian Grünbichler <f.gruenbichler at proxmox.com>:

>
> > Wolfgang Link <w.link at proxmox.com> hat am 10. Mai 2016 um 11:13
> geschrieben:
> >
> >
> > If we make a linked clone the CT must be a template so it is not allowed
> to run.
> > If we make a full clone, it is safer to have the CT offline.
>
> shouldn't it also be possible to freeze the container for full clones?
> that prevents modifications to the container file systems  by the
> container, so we can safely copy everything to the clone and then unfreeze
> the original container again. it would even be possible to use the same
> two-step rsync mechanism from suspend backups to minimize downtime.. for
> containers where freeze is problematic (i.e., the explicitly not
> recommended "FUSE in container" setups) the full clones without freezing
> are still possible by simply shutting down the container.
>
> _______________________________________________
> pve-devel mailing list
> pve-devel at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>