On Fri, Jul 31, 2026 at 04:57:06PM +0200, Lee Garrett wrote:
> Hi Andrea,
> 
> Please consider shipping the modular per-driver daemons (virtqemud etc.,
> plus virtproxyd for socket compatibility) in a new binary package, so
> they're available as alternative to the monolithic libvirtd. This is
> separate from any decision about the default preset.
> 
> Rationale:
> 
> - Upstream treats libvirtd as legacy, replaced by the modular virt*d
>   daemons, with removal planned. [0][1]
> - Fedora (since F35) [2], RHEL 9 [3], and SLES 15 SP6 [4] already ship
>   and default to the modular daemons.
> - Upstream is adding support to build without libvirtd entirely (Feb
>   2026 RFC: -Ddriver_libvirtd=disabled). [5]
> 
> Shipping the modular daemons now lets users opt in and keeps Debian
> ready for when upstream drops libvirtd. Happy to help test.

I don't expect upstream to actually drop the monolithic daemon any
time soon, especially now that it's possible to opt out of it being
built.

Anyway, the plan is definitely to ship the modular daemons in Debian.
I want to (and should be able to) make it happen in forky.

Each daemon will be included in the binary package for the
corresponding driver, same as upstream and Fedora. The monolithic
daemon will probably remain the default for a while longer, but
opting into a modular setup is fairly easy once the package contains
all the bits you need.

-- 
Andrea Bolognani <[email protected]>
Resistance is futile, you will be garbage collected.

Attachment: signature.asc
Description: PGP signature

Reply via email to