Your message dated Fri, 3 Apr 2020 10:32:27 +0200
with message-id <[email protected]>
and subject line Re: Bug#809389: [Pkg-libvirt-maintainers] Bug#809389: 
libvirt-daemon-system: enable libvirtd through socket activation
has caused the Debian Bug report #809389,
regarding libvirt-daemon-system: enable libvirtd through socket activation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
809389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809389
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libvirt-daemon-system
Version: 1.2.21-2
Severity: wishlist

Hello,

Do you think it'd make sense to have the libvirtd.socket activated by
default. libvirt can be used by users as a Workstation Hypervisor
replacement like VirtualBox and VMWare Workstation.

Having the daemon running all the time, when it can do the same through
systemd socket activation, might be more efficient.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.3+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libvirt-daemon-system depends on:
ii  adduser              3.113+nmu3
ii  gettext-base         0.19.6-1
ii  init-system-helpers  1.24
ii  libapparmor1         2.10-2+b1
ii  libaudit1            1:2.4.4-4
ii  libblkid1            2.27.1-1
ii  libc6                2.21-6
ii  libcap-ng0           0.7.7-1
ii  libdbus-1-3          1.10.6-1
ii  libdevmapper1.02.1   2:1.02.114-1
ii  libnl-3-200          3.2.26-1
ii  libnl-route-3-200    3.2.26-1
ii  libnuma1             2.0.11-1
ii  librados2            0.80.10-2
ii  librbd1              0.80.10-2
ii  libselinux1          2.4-3
ii  libsystemd0          228-2+b1
ii  libvirt-clients      1.2.21-2
ii  libvirt-daemon       1.2.21-2
ii  libvirt0             1.2.21-2
ii  libxml2              2.9.3+dfsg1-1
ii  libyajl2             2.1.0-2
ii  logrotate            3.8.7-2
ii  policykit-1          0.105-14

Versions of packages libvirt-daemon-system recommends:
ii  bridge-utils  1.5-9
ii  dmidecode     3.0-2
ii  dnsmasq-base  2.75-1
ii  ebtables      2.0.10.4-3
ii  iproute2      4.3.0-1
ii  iptables      1.4.21-2+b1
ii  parted        3.2-12
pn  pm-utils      <none>

Versions of packages libvirt-daemon-system suggests:
pn  apparmor    <none>
pn  auditd      <none>
pn  nfs-common  <none>
pn  radvd       <none>
ii  systemd     228-2+b1
ii  systemtap   2.9-2

-- Configuration Files:
/etc/libvirt/qemu.conf [Errno 13] Permission denied: u'/etc/libvirt/qemu.conf'
/etc/libvirt/qemu/networks/default.xml [Errno 2] No such file or directory: 
u'/etc/libvirt/qemu/networks/default.xml'

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: libvirt/6.0.0-1

Hi,
On Fri, Jun 17, 2016 at 06:37:34PM +0530, Ritesh Raj Sarraf wrote:
> 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.

Socket activation is now there and we're shipping it, for making it the
default see #955536.
Cheers,
 -- Guido

> 
> 
> 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

--- End Message ---

Reply via email to