On Tue, Sep 17, 2019 at 05:03:55PM +1000, Michael Chapman wrote:
A couple of bugs were encountered using socket activated libvirtd on CentOS 7:
It actually hits on new distros too
- 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.
Opps.
- The wrong name was used when checking whether libvirtd-tls.socket was passed to libvirtd, leading to this socket not being properly registered.
Due to the refactoring for the split daemons being messed up. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|