© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Hi Thierry,
I don't know of any Ubuntu specific lack of support, please let me know if there is.
What I know about that - and furthermore for the benefit of everybody else getting - can be found at [1]. That page is a nice summary on the topic. Related to that also are the use-cases from [2]. They might be slightly outdated, I think I saw a new format being ,snapshot=external.
TL;DR
- internal snapshots are within qcow2 - fully supported in libvirt
- external snapshots (qemu backing chains) are in favor qemu
- libvirt doesn't fully support all operations on external snapshot
I didn't track this area in particular but didn't see it show up as a new major item (and IMHO it would be one). On one hand the changelog never held it as major feature in recent years, on the other hand the wording of (internal) snapshot != (external) snapshot in libvirt makes it harder to search for it.
Thereby I think it isn't "fully supported" in any version of libvirt yet other than with the workarounds and use-cases described on [1][2] that worked already with the libvirt that was released with Xenial.
Now if such a feature would be developed upstream (or if I missed that it already is but under a different name) your general question gets more important. In understood it as "how to get a newer but supported virtualization stack while still staying at the LTS release", to do so I'd recommend you take a look at [3].
Unless I misunderstood you (I beg your pardon in that case and ask you to explain) I think this is a upstream feature request and therefore I classify the bug as that for now.
[1]: https:/
[2]: http://
[3]: https:/