Control: tag -1 forwarded https://bugzilla.redhat.com/show_bug.cgi?id=1326136
In the past releases, both Upstream and Debian, dropped libvirtd socket activation as it was feature in-complete. The referenced bugzilla is the new RFE for the same request as my bug report. On Wed, 2015-12-30 at 14:42 +0100, Guido Günther wrote: > 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. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
