This bug came up in triage, and I tried to reproduce it on xenial with
libvirt-bin 1.3.1-1ubuntu10.29, which is quite older than the one from
2016 when this bug was opened.
root@xenial-socket-restart:~# virsh list
Id Name State
----------------------------------------------------
root@xenial-socket-restart:~# l /var/run/libvirt/libvirt-sock
srwxrwx--- 1 root libvirtd 0 Jan 14 14:44 /var/run/libvirt/libvirt-sock
root@xenial-socket-restart:~# service libvirt-bin restart
root@xenial-socket-restart:~# virsh list
Id Name State
----------------------------------------------------
root@xenial-socket-restart:~# l /var/run/libvirt/libvirt-sock
srwxrwx--- 1 root libvirtd 0 Jan 14 14:45 /var/run/libvirt/libvirt-sock
root@xenial-socket-restart:~#
I'll note, however:
- I tried this in a lxd container, where I wouldn't expect to be able to launch
virtual machines out-of-the-box, but it's enough to see if the daemon is
running and listening
- the second virsh list, right after the restart, took a while, and the cpu
usage got high for a few seconds, but settled down a bit later. I have a few
DENIED messages in dmesg, probably due to my use of a lxd container for this
test.
Since there have been many changes to the package since 1.3.1-1ubuntu10,
and given that the simple steps above didn't reproduce the issue, I'll
mark the bug as incpmplete. If someone can reproduce it with the current
version of the package, then please add this information to the bug,
including steps needed to see the problem happening.
Thanks!
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583688
Title:
libvirt-sock not recreated on service restart
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1583688/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
