Proxmox Committing Changes to an Image (template)

[pgro]

Hi,

With qemu-img you can create a template and then chain it with rest of clones. Later you can use commit command to commit changes back to original template. Is that possible with Proxmox?

EG:

qemu-img info –backing-chain /var/lib/libvirt/images/test.qcow2
.
.
sudo qemu-img commit /var/lib/libvirt/images/test.qcow2 Image committed

Resource : https://access.redhat.com/documenta...using_qemu_img-committing_changes_to_an_image

Thank you

 

[dcsapak]

no, and i don't think we can properly implement that, since it's a feature of qcow2 images and would not work with other storages e.g. zfs/ceph
we generally don't want to expose features when it's only working for a (very) limited set of storage types

but you can ofc open a feature request, maybe someone else on the team has a different opinion: https://bugzilla.proxmox.com

 

[fiona]

Hi,
also, in Proxmox VE template images are (treated as) immutable and the intended use case is to create multiple linked clones from the same template, rather than a chain of clones. I don't think commuting back would work nicely for that scenario.

 

[pgro]

Hi Fiona and thank you for your reply

So also this one need cqow2 ?
https://access.redhat.com/documenta...-using_blockcommit_to_shorten_a_backing_chain

 

[fiona]

Hi Fiona and thank you for your reply

So also this one need cqow2 ?
https://access.redhat.com/documenta...-using_blockcommit_to_shorten_a_backing_chain

Sorry, I don't understand the question. Proxmox VE doesn't use virsh or blockcommit. Yes, to use qemu-img commit, you need qcow2. But I already told you why this is not a good idea in Proxmox VE. You also might want to pay attention to the warning on the page you linked.