I figured it out - I used emu-img convert -O qcow2 ….
Antoine Boucher [email protected] [o] +1-226-505-9734 www.haltondc.com “Data security made simple”  Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential, and may be privileged. If you are not the intended recipient, you are hereby notified that any review, retransmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, and delete this message and any attachments from your system. > On Oct 25, 2025, at 3:37 PM, Antoine Boucher <[email protected]> wrote: > > Or is it the other way around - which would make more sense? > > > >> On Oct 25, 2025, at 3:14 PM, Antoine Boucher <[email protected]> wrote: >> >> Greetings, >> >> >> >> >> I have various QEMU/KVM snapshots on my storage pools that CloudStack does >> not seem to recognize. I assume this is the result of ultimately failed >> snapshots for various reasons. If I run qemu-img info on the "snapshot" and >> on what ACS believes is the VM's root disk, it clearly shows the backing >> file. Assuming I backup both files, should or could I perform a qemu-img >> commit on this snapshot to flatten it back to its parent, and then rename >> the parent to the snapshot's UUID to restore it to a clean volume? >> >> >> >> Regards, >> >> Antoine >> >> >> >
