can't snapshot uvtool created vms

[Tycho Andersen]

$ virsh snapshot-create-as criu2
error: unsupported configuration: internal snapshot for disk vdb unsupported for storage type raw

looks like the cloud-init data source should be of a different type.

[Robie Basak (racb)]

Workaround: add <readonly/> to the <disk> definition after instance creation (eg. with "virsh edit <name>").

Solution: uvtool should do this automatically. IIRC it's iso9660 so is read-only as far as userspace is concerned anyway, but libvirt doesn't know that.

[Theodotos Andreou (theodotos)]

I couldn't get the <readonly/> workaround to work. A better solution is described here:

https://askubuntu.com/questions/540188/what-is-uvtool-second-virtual-disk-for-and-how-does-it-prevent-vm-snapshots

[Chris J Arges (arges)]

This fixed it for me, can it be merged?
https://code.launchpad.net/~arges/uvtool/ds-qcow2

[Juan Rubén (rubenmv)]

Possible solution: check line 215 of kvm.py vs cloud-localds syntax for disk format.

Methinks the "=" is not needed, so cloud-localds defaults to raw?

[Robie Basak (racb)]

This is actually fixed in git master, available from the PPA. Sorry I didn't update the bug before.

There is a secondary problem now, which is that if snapshots exist then "uvt-kvm destroy <vm>" fails. This can be worked around by deleting the snapshot first.