[pve-devel] kvm disk template implementation ideas

[Dietmar Maurer]

> >>A simply storage scan does not work, because we also want a snapshot
> >>of the VM configuration!
> Ah ok, I miss that. I think you were talking about simple disk snapshot.

No, we want full-featured VM snapshots ;-)
 
> >>My idea was to extend the <vmid>.conf file to include a copy of the config
> >>for each snapshot:
> 
> >>----START----
> >># The current config is on top
> >>mem: 1024
> >>parent: snap2
> >>
> >>[snap3]
> >>mem: 512
> >>parent: snap1
> >>
> >>[snap2]
> >>mem:128
> >>parent: snap1
> >>
> >>[snap1]
> >>mem: 256
> 
> Yes, that can be great.
> how do you see disk part ?

Not sure if I understand your question correctly. The disks are part of the config,
so each snapshot simply point to the snapshotted volume somehow:

- either explicit: by using different volume names
- or implicit: we generate the real snapshot volume names as F(volid, snapshotname)

----impicit example----
# The current config is on top
mem: 1024
ide0: local:100/vm-100-disk-1.qcow2
parent: snap1

 [snap1]
mem: 256
ide0: local:100/vm-100-disk-1.qcow2
----END----


Or the other way:

----expicit example----
# The current config is on top
mem: 1024
ide0: local:100/vm-100-disk-1.qcow2
parent: snap1

 [snap1]
mem: 256
ide0: local:100/vm-snap1-100-disk-1.qcow2
----END----