If "restricting features after upgrade" is not an option until we came up upstream with a preferred approach to fix this the workarounds are: - migrate away and back for upgrades (general practice, but sometimes impossible e.g. due to passthrough) - the .so by using the functionality before upgrade (e.g. attach and detach a rbd device). I guess there could even be a valid config but invalid target which would achieve the same without the guest noticing.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847361 Title: Upgrade of qemu binaries causes running instances not able to dynamically load modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847361/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
