And while I was looking to spawn that discussion see what I've found: upstream Bug & Discussion: https://bugzilla.redhat.com/show_bug.cgi?id=1725330
And the fix was dropping the mention (and some remaining code) of that ability: https://github.com/virt-manager/virt-manager/commit/140a1f3b15d47ea5d2d56bdf56d0484419023280 Gladly the content and discussion there agree to my gut feeling I expressed above "it was never a safe idea to begin with, because disk contents could be in an inconsistent state" especially in your case with qcow "... other format that is not possible as e.g. qemu is caching the image metadata (qcow2 internals)". We are on the latest release (2.2.1) and ill pick this up (no need to rush or SRU for this IMHO) with the next merge once upstream releases a new version. ** Bug watch added: Red Hat Bugzilla #1725330 https://bugzilla.redhat.com/show_bug.cgi?id=1725330 ** Also affects: virt-manager via https://bugzilla.redhat.com/show_bug.cgi?id=1725330 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873887 Title: virt-clone fails on a suspended (paused) guest, whereas documentation claims the clone should be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1873887/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
