(Un)fortunately, during focal-proposed testing today, a corner case was identified (late), which will require changes.
Some of the qemuProcessReconnect() threads finished within the timeout but others didn't. The ones which didn't were waiting on a reply back from the QEMU monitor, but that never fires because it is processed/delivered by the main event loop, which is already stopped at libvirtd level by the time the driver-level qemuStateCleanup() runs (where we wait). The libvirt shutdown does happen after the timeout, but this is slow and not as planned. I've been considering design options to address it and will submit an incremental upload. Apologies for the inconvenience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059272 Title: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2059272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
