A couple of bugs were encountered using socket activated libvirtd on
CentOS 7:
- When resolving a tls_port/tcp_port from the config file (needed even
when using socket activation on systemd < v227), the port endianness
was incorrect.
- The wrong name was used when checking whether libvirtd-tls.socket
was passed to libvirtd, leading to this socket not being properly
registered.
Michael Chapman (2):
util: fix byte order of port in virSocketAddrResolveService
remote: fix registration of TLS socket
src/remote/remote_daemon.c | 2 +-
src/util/virsocketaddr.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
--
2.20.1