[Pkg-libvirt-maintainers] Bug#809389: Bug#809389: libvirt-daemon-system: enable libvirtd through socket activation

Guido Günther agx at sigxcpu.org
Wed Dec 30 13:42:00 UTC 2015


On Wed, Dec 30, 2015 at 06:57:11PM +0530, Ritesh Raj Sarraf wrote:
> On Wed, 2015-12-30 at 14:08 +0100, Guido Günther wrote:
> > > Having the daemon running all the time, when it can do the same
> > through
> > > systemd socket activation, might be more efficient.
> > 
> > If you don't want to have the daemon running you can just remove the
> > libvirt-daemon-system package.
> 
> I think I put the example with only half the libvirt components.
> 
> AFAIK, virt-manager works by connecting to libvirtd. And so does GNOME
> Boxes. Without libvirtd in the background, they won't work.

virt-manager/boxes connect to:

    a) the system libvirtd if you use e.g. qemu:///system
    b) the libvirtd run as your user if you use qemu:///session

You need the systemd managed service for a) only so if you use b) you
can safely remove libvirt-daemon-system. gnome-boxes was initially the
reason for doing that split in the first place.

> I can manually start the libvirtd.socket, after which, it'd dynamically
> start the daemon. But given that the libvirtd.socket is installed as
> 'static', it cannot be enabled/disabled.

I do wonder why that is though. There are no other units depending on it.

Cheers,
 -- Guido



More information about the Pkg-libvirt-maintainers mailing list