Hacker News new | ask | show | jobs
by easton 1136 days ago
Have I been asleep at the wheel or is this libvirtd change a RHEL only thing? Last few times I spun up libvirt on Ubuntu, there was only libvirtd. Maybe it spins up the non-monolithic services in the background and I didn’t notice?
1 comments

The work to split into multiple daemons started a few years ago.

https://gitlab.com/libvirt/libvirt/-/blob/9b8bb536ff999fa61e...

On OpenSUSE Tumbleweed I do have the individual daemons' service units (`virtqemud.service` etc from the `libvirt-daemon-driver-qemu` package etc) but I still use the original `libvirtd.service` that runs `/usr/sbin/libvirtd`. I might look into switching over the weekend.

    systemctl stop 'libvirtd*.service'
    systemctl disable --now 'libvirtd*.socket'
    systemctl enable --now virt{qemu,network,storage,nodedev,log}d.socket
Went without a hitch. `virt-manager` still works without the need for `virtproxyd`.