[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
IdName State
@Richard
IMHO likely a different issue.
This here was of the 16.04 time and some odd ordering of the services that
provided socket activation.
We don't use socket activation anymore in 19.10 therefore I'd think this
would be a better a new bug.
In on this new bug directly add answers to:
- is
On Ubuntu 19.10 I get the following error running
$sudo virtsh list -all
error: failed to connect to the hypervisor
error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such
file or directory
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Patch removed: "unit file patch for /lib/systemd/system/libvirt-bin.service"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1583688/+attachment/4678193/+files/libvirt-bin.service.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The attachment "unit file patch for /lib/systemd/system/libvirt-
bin.service" seems to be a patch. If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message
Based on my experiments, I'd like to propose this patch.
** Patch added: "unit file patch for /lib/systemd/system/libvirt-bin.service"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1583688/+attachment/4678193/+files/libvirt-bin.service.patch
--
You received this bug notification
playing a bit with the libvirt-bin systemd units I've came to this order
of things that ensures the sockets are created:
root@os-gate-u16:~# systemctl stop libvirt-bin.service ; systemctl stop
libvirt-bin.socket ; systemctl start libvirt-bin.socket; systemctl start
libvirt-bin.service ; lsof
btw using systemctl directly doesn't lead to the socket present:
root@os-gate-u16:~# systemctl restart libvirt-bin.service ; lsof
/var/run/libvirt/libvirt-sock
lsof: status error on /run/libvirt/libvirt-sock: No such file or directory |
grep libvirtd
lsof 4.89
latest revision:
Hi,
seems I'm affected by this as well (ran into it trying devstack in 16.4 LTS).
Service libvirt-bin stop; service libvirt-bin start fixed this for me.
As soon as I do service libvirt-bin restart the socket vanishes again from
/var/lib/libvirt for me.
The odd thing is, lsof -p shows the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
--
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:
Sure, these are the logs after running the restart command:
May 20 09:26:48 XXX-XXX-XXX-XXX systemd[1]: Stopping Virtualization daemon...
May 20 09:26:48 XXX-XXX-XXX-XXX systemd[1]: Stopped Virtualization daemon.
May 20 09:26:48 XXX-XXX-XXX-XXX systemd[1]: Starting Virtualization daemon...
May 20
12 matches
Mail list logo
