Equipped with that we can make some tests...
On one hand libvirt, if there is no API or domain load will shutdown after 120
seconds anyway.
I checked and just waiting will make it work.
I see the socket fall back to:
● libvirtd.socket - libvirt legacy monolithic daemon socket
...
Active: active (listening)
And then from this state it immediately works:
$ sudo apt install libvirt-daemon-driver-lxc
$ virsh --connect lxc:/// list
error: failed to connect to the hypervisor
error: no connection driver available for lxc:///
But surely if a host is rather active (domains and api calls up) or has
an open connection (like virt-manager) it will never recycle. And I can
see that users would expect it to work after install (if possible).
---
The mentioned reload defined as
"On receipt of SIGHUP libvirtd will reload its configuration."
Will NOT recycle the process.
I've seen e.g. my:
560007 /usr/sbin/libvirtd --timeout 120
stay as is, but get new entries to read the conf:
...
Jan 07 10:34:51 Keschdeichel dnsmasq[2696]: read /etc/hosts - 13 names
Jan 07 10:34:51 Keschdeichel dnsmasq[2696]: read
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 names
Jan 07 10:34:51 Keschdeichel dnsmasq-dhcp[2696]: read
/var/lib/libvirt/dnsmasq/default.hostsfile
Therefore as you said "systemctl reload" isn't enough to make it realize there
is something new.
Yet on the other hand restarting it can be heavy.
We are doing so on any package upgrade of libvirt-daemon-system itself, the
question now is if there is a way in between from reload and restarting that is
better in this case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092350
Title:
virt-manager does not notice libvirt-daemon-driver-lxc being installed
until reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2092350/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
