Comment 4 for bug 1738834

Another way to hit this upgrade path is Xenial using libvirt and then upgrading to Cloud-Archive Pike (Artful based).

Since we already have 18.04/Queens which also is longer supported I tried with that.

This most likely is due to "--no-restart-on-upgrade" that is used for virtlogd.
Which was actually added that way in Debian to avoid issues with guest logs due to the restart.

I agree to Andreas that the most common case is a release-upgrade, but still I'd love to see this solved.

This seems to be almost like a no-way-out issue, quoting from upstream changelog (a bit older in 2016).

 45221 »···virtlogd: Don't stop or restart along with libvirtd
 45222 »···Commit 839a060 tied the lifecycle of virtlogd more
 45223 »···closely to that of libvirtd. Unfortunately, while starting
 45224 »···virtlogd when libvirtd is started is definitely a good idea,
 45225 »···restarting virtlogd or shutting it down at any time outside
 45226 »···of system poweroff is not.
 45227
 45228 »···Revert part of that commit by removing the PartOf= lines,
 45229 »···meaning that only startup requests will be propagated from
 45230 »···libvirtd to virtlogd.

Somewhere in the back of my mind is something about getting virtlogd reload/reopen files as needed, but I can't rememeber atm where/what to look for.

This needs some checks to find a way how to make it
a) not fail due to a restart
b) not fail due to not being restarts
which seem opposite until we have found a way to do so.