Bug 2193055

There are many changes done by @crobinso since last F38 build. This caused problem and now when I updated my F38 Silverblue to F39 Silverblue, I am not able to run virtual machines. I need to fix few things like described in initial comment here like pulling libvirt-daemon then starting libvirtd service along with virtnetworkd.socket service. Finally my VM's are back to work.

This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

This is expected since libvirt switched to defaulting to modular daemons. More details here: https://fedoraproject.org/wiki/Changes/LibvirtModularDaemons

Basically, monolithic libvirtd.service is not installed by default, in favor of fine grained daemons virtqemud, virtnetworkd, virtstoraged, etc. So it's expected that the combined libvirtd binary is not pulled in by the libvirt-daemon-kvm metapackage.

@

@pnemade it sounds like you're seeing an upgrade issue, there could be a bug there when going from f38 to f39. given the above comment, can you isolate what specifically went wrong? did you have libvirt-daemon installed before but now it's not working?

There has been some libvirt daemon weirdness caused by a systemd regression that is since fixed, maybe you were hitting that: https://github.com/systemd/systemd/issues/27953

Luckily i have saved the terminal log of upgrading Fedora 38 Silverblue to Fedora 39 Silverblue

$ cat Silverblue-38-to-39.txt |grep libvirt
Upgraded:
  libvirt-client 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-config-network 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-driver-interface 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-driver-network 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-driver-nodedev 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-driver-nwfilter 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-driver-qemu 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-driver-secret 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-driver-storage 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-driver-storage-core 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-driver-storage-disk 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-driver-storage-gluster 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-driver-storage-iscsi 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-driver-storage-iscsi-direct 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-driver-storage-logical 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-driver-storage-mpath 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-driver-storage-rbd 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-driver-storage-scsi 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-driver-storage-zfs 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-daemon-kvm 9.0.0-3.fc38 -> 9.6.0-1.fc39
  libvirt-glib 4.0.0-8.fc38 -> 4.0.0-9.fc39
  libvirt-libs 9.0.0-3.fc38 -> 9.6.0-1.fc39
  python3-libvirt 9.0.0-2.fc38 -> 9.6.0-1.fc39
Removed:
  libvirt-daemon-9.0.0-3.fc38.x86_64
Added:
  libvirt-daemon-common-9.6.0-1.fc39.x86_64
  libvirt-daemon-lock-9.6.0-1.fc39.x86_64
  libvirt-daemon-log-9.6.0-1.fc39.x86_64
  libvirt-daemon-plugin-lockd-9.6.0-1.fc39.x86_64
  libvirt-daemon-proxy-9.6.0-1.fc39.x86_64

About systemd package, I see below in logs, so systemd was not the issue when my system is upgraded.
Upgraded:
  systemd 253.7-1.fc38 -> 254-1.fc39


I don't know if this was correct upgrade happened for libvirt packages or there was an issue with the F39 compose which I used to upgrade.

After that I managed to get libvirt service up and running by installing libvirt-daemon package. I also need to enable other services virtnetworkd.service and virtstoraged.service

I can't find anything in libvirt spec that should have caused libvirt-daemon to be removed.

What command did you use to update silverblue? Maybe whatever method it uses removed libvirt-daemon, since it's not the default setup anymore.

I don't really know where to check to figure that out though.