Comment 4 for bug 1869796

In your logs I've found the following two interesting pieces:

Mar 30 20:44:55 millbarge systemd[1]: libvirtd.service: Found left-over process 3054 (dnsmasq) in control group while starting unit. Ignoring.
=> That is ok, some things are expected to live over to the new restarted service

Mar 30 20:44:55 millbarge systemd[1]: libvirtd-ro.socket: Succeeded.
Mar 30 20:44:55 millbarge systemd[1]: Closed Libvirt local read-only socket.
Mar 30 20:44:55 millbarge systemd[1]: Stopping Libvirt local read-only socket.
Mar 30 20:44:55 millbarge systemd[1]: libvirtd-ro.socket: Socket service libvirtd.service already active, refusing.

That might be related to your issue, but I'm not entirely sure.

Unless you restarted plenty of services already could you run the following pelase:
 $ systemctl status $(for f in $(dpkg -L libvirt-daemon-system | grep systemd | grep -e socket -e service); do basename $f; done | xargs)

I can then compare that with new-installs and upgrades that I can retry.

Also was your upgrade from
- former focal version
- from eoan
- from bionic
?