Description of problem:
When setting keepalive_required=1, libvirtd will refuse all the clients even if the client supports keepalive.
Version-Release number of selected component :
Steps to Reproduce:
1.Set keepalive_required=1 in libvirtd.conf on host A, restart libvirtd service.
2.Connect to the libvirtd of host A:
# virsh -c qemu+tcp://10.66.6.6/system
error: failed to connect to the hypervisor
error: operation failed: keepalive support is required to connect
As step2, libvirtd refused the client connection.
As virsh client supports replying for server keepalives, it should connect successfully.
Patch proposed upstream:
Fixed upstream by v1.2.18-61-ga8743c39389b:
Author: Martin Kletzander <email@example.com>
Date: Mon Jul 20 14:51:24 2015 +0200
rpc: Remove keepalive_required option
Verify this bug with libvirt-1.2.17-6.el7, could found the clear explanation that the keepalive_required option has been removed in libvirtd.conf, also found the corresponding code has been disabled, so we could verify this bug right now.
# These configuration options are no longer used. There is no way to
# restrict such clients from connecting since they first need to
# connect in order to ask for keepalive.
#keepalive_required = 1
#admin_keepalive_required = 1
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.