[Pkg-libvirt-maintainers] Bug#872573: Stopping libvirtd.service does not properly stop all (dnsmasq) processes
Guido Günther
agx at sigxcpu.org
Mon Sep 11 06:07:45 UTC 2017
control: tags -1 +wontfix
Hi Micheal,
On Fri, Aug 18, 2017 at 08:47:09PM +0200, Michael Biebl wrote:
> Package: libvirt-daemon-system
> Version: 3.6.0-1
> Severity: normal
> File: /lib/systemd/system/libvirtd.service
>
> libvirtd.service uses KillMode=process, this means, it's up to the main
> process to kill all child processes properly. This doesn't seem to be
> the case for libvirtd
>
> # systemctl status libvirtd
> ● libvirtd.service - Virtualization daemon
> Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
> Active: active (running) since Fri 2017-08-18 20:08:30 CEST; 37min ago
> Docs: man:libvirtd(8)
> http://libvirt.org
> Main PID: 689 (libvirtd)
> Tasks: 18 (limit: 32768)
> CGroup: /system.slice/libvirtd.service
> ├─ 689 /usr/sbin/libvirtd
> ├─1529 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
> └─1530 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
>
> # systemctl stop libvirtd
> # systemctl status libvirtd
> ● libvirtd.service - Virtualization daemon
> Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
> Active: inactive (dead) since Fri 2017-08-18 20:46:35 CEST; 1s ago
> Docs: man:libvirtd(8)
> http://libvirt.org
> Process: 689 ExecStart=/usr/sbin/libvirtd $libvirtd_opts (code=exited, status=0/SUCCESS)
> Main PID: 689 (code=exited, status=0/SUCCESS)
> Tasks: 2 (limit: 32768)
> CGroup: /system.slice/libvirtd.service
> ├─1529 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
> └─1530 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
>
> See, how the dnsmasq processes are still running after stopping the
> service.
This is itentional since the networks continue to run. Once you stop the
network the dnsmasq instance goes away too. Otherwise daemon restarts
would break VM connectivity.
Cheers,
-- Guido
More information about the Pkg-libvirt-maintainers
mailing list