Maybe your new examples have used the actual defaults (q35 and sata cdrom) and therefore the recent error messages are that way. But even assuming that still too much is somewhat odd here and I fail to recreate the issue :-/
Sorry, I really tried to get a hold on this issue but there must be more to your use case or your system setup (as by now we've identified quite a bunch of odd details compared to a standard 20.04 system behavior). I was looking for similar report and found this https://bugzilla.redhat.com/show_bug.cgi?id=1824722 It looks quite similar to what you see. If it is that it would be an yet-to-be-solved upstream case. Could you sort out by goign through the details there if that is really exactly the case you are facing? And if you are maybe chime in there to revive the bug and driving it to a resolution. P.S. the bug there is around guest resets which don't match your use- case AFAICS, but still it is similar enough to have a look ** Bug watch added: Red Hat Bugzilla #1824722 https://bugzilla.redhat.com/show_bug.cgi?id=1824722 ** Also affects: libvirt (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1824722 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/1930398 Title: libvirtd unable to execute QEMU command 'blockdev-remove-medium' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1930398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
