Type 1 seems easy to implement, but type 2 looks clumsy.
Yes, indeed 1 is easy. 2 need more work and can a little more tricky,because is
like a qcow2 external snapshot
But first, why do I want to clone a VM? Please can you elaborate on
the usage scenario first?
Cloning vm is a current
But first, why do I want to clone a VM? Please can you elaborate on
the usage scenario first?
Cloning vm is a current scenario in enterprise, generally, you have a basevm
you want to duplicate in 1 second.
Other scenario can be vdi desktop, you can clone in live a vm if a user need a
like a linux image or windows image,
you want to do security updates or install new packages on the image, then
make a new snapshot, and clone from this new snapshot.
You want to clone a specific snapshot?
Live cloning can be also good to duplicate a vm to do tests in parallel.
So, I
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.
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
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
1.) create template: create a read-only snapshot of all used VM disks
We can also have several different methods to create templates:
a.) Create a template from any existing VM
b.) Create a template from a VM backup file (file import possible)
other ideas?
Ah, I see (But it is unrelated to our snapshot implementation inside
qemu-server).
So cloning is a 2-step process in general:
1.) create template: create a read-only snapshot of all used VM disks
2.) clone template: make a writable copy of above templates
Yes, I think this is perfect
The
yes.
one note : for nfs,directory,filename/path can't be change after cloning, as
new qcow2 file have parent path/file hardcoded inside it.
Yes, that is why volume templates will use a special path/name (They also has
no owner VM).
We will also make the file permissions read-only.
2.)
So IMHO, 'copy' and 'clone' are different features?
For me copy = full clone
but maybe full clone = copy of the same storage type ?
each hypersivor/solution have differents terms for them...
- Mail original -
De: Dietmar Maurer diet...@proxmox.com
À: Alexandre DERUMIER
