Comment 19 for bug 2059272

(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.