Is there any reason why this wasnt commited? or as valid ? removing the
-d option from /etc/default/libvirt-bin fixed the issue for me too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567272
Title:
Yes, removing '-d' fixed it, thank you
** Changed in: libvirt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567272
Title:
systemd claims libvirt-bin is dead
I think the problem here is that /etc/default/libvirt-bin has not been
changed and still forces "-d" as a start option. This causes the
libvirtd process to (unexpectedly from systemd's point of view) fork.
Note that the pid reported as the service (20385) is not the one under
which the daemon runs
** Description changed:
- On Xenial systemd is not reporting the state of libvirtd properly or
+ On Xenial, systemd is not reporting the state of libvirtd properly or
shutting down on request.
# pgrep libvirtd
# systemctl start libvirt-bin.service
# systemctl status libvirt-bin.service
