On Mon, Jun 24, 2024 at 11:42:46AM +0100, Daniel P. Berrangé wrote:
On Sat, Jun 22, 2024 at 07:42:00PM +0000, procmem@riseup.net wrote:
Thus if you're not intending to use the libvirt virtual network feature, simply don't install its modyle, and then libvirtd will see the module doesn't exist, and skip the dlopen.
That sounds like something people would do who compile from source code?
We're using libvirtd (9.0.0-4) from Debian package sources. [1]
This is possible on Fedora/RHEL with the RPM packages, but it seems Debian just bundle it all into one package :-(
https://packages.debian.org/bookworm/amd64/libvirt-daemon/filelist
FYI this has been possible in Debian unstable/testing for a few months now, specifically from version 10.6.0-2 forward. Unfortunately it's going to be a long while before those changes are included in a stable release.
If you're using the new modular daemons, then even if installed, the virtnetworkd daemon won't get launched unless some guest is configured to use it. So if you're intending to setup network bridges yourself, virtnetworkd shouldn't run.
That is libvirtd 9.x or 10.x?
Is there a chance that something is wrong with the libvirtd compilation settings by Debian's packaging?
Yes, it seems debian is intentionally not shipping them :-(
It's not a matter of intention as much as it is one of resources. I maintain the Debian package in my spare time and I just haven't gotten around to implement this specific transition yet. It'll come eventually. -- Andrea Bolognani / Red Hat / Virtualization