I think this got another side effect.
needrestart detects services in their scope and so it finds dnsmasq processes
using outdated libs.
Once it does it will flag "libvirtd.service" as using outdated binaries,
essentially every time from that moment as - due to the lack of restarting them
-
** Changed in: libvirt (Ubuntu)
Status: New => Triaged
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818711
Title:
never
Meh, I'd rather see /usr/lib/libvirt/libvirt-guests.sh at the end of
stop, iterate across `virsh net-list` and call `virsh net-destroy` on
them.
However, this is too heavy weight for shutdown. As net-destroy does much
more than just killing dnsmasq. It appears to remove the bridge & nics
too
Currently (quite a while actually [3]) the ordering on shutdown is like this:
libvirtd -> domain -> virt-guest-shutdown.target -> save-restore.service
And as Steve mentioned "save-restore" is to allow to shutdown or save guest
state - and that not only via the default libvirt-guests.service but
> I don't know why libvirt has KillMode=process, but my guess is
> that one ideally wants to be able to restart libvirt without
> killing VMs / dnsmasq state. However, when doing shutdown,
> these should be really killed.
Yes, but the VM shutdown should also be managed by libvirt itself, since
I don't believe I do, nor does the surrounding context look similar.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818711
Title:
never kills dnsmasq servers
To manage notifications about this bug
Does your libvirt have this patch?
https://www.redhat.com/archives/libvir-list/2019-January/msg00389.html
If so, your dnsmasq profile may need updated to accommodate that change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
