Bug 1402507

Description of problem:
I am not absolutely sure if it's a bug, or simply a missing feature. Anyway, here it is:

Satellite 6.2.4 server on my test environment is installed as a KVM virtual machine. I have configured the KVM of the host as a Compute Resource and host provisioning (without any Capsule/Foreman Proxy) works just fine. However, I want to use the DHCP/DNS provided by libvirt itself in order to control the IPs/hostnames of my new boxes. 

I have installed Satellite 6 with the following options:

satellite-installer -S satellite  --foreman-proxy-dhcp-provider virsh --foreman-proxy-dhcp-server kvmbox.testenv --foreman-proxy-dns-server kvmbox.testenv --foreman-proxy-dns-provider virsh --foreman-proxy-dns true --foreman-proxy-dhcp true --foreman-proxy-dhcp-interface eth0

The relevant configuration files are:

---
# Enable DHCP management
# Can be true, false, or http/https to enable just one of the protocols
:enabled: https

# valid providers:
#   - dhcp_isc (ISC dhcp server)
#   - dhcp_native_ms (Microsoft native implementation)
#   - dhcp_virsh (simple implementation for libvirt)
:use_provider: dhcp_virsh
:server: kvmbox.testenv
# subnets restricts the subnets queried to a subset, to reduce the query time.
#:subnets: [192.168.205.0/255.255.255.128, 192.168.205.128/255.255.255.128]

---
# DNS management

:enabled: https
# valid providers:
#   dns_dnscmd (Microsoft Windows native implementation)
#   dns_nsupdate
#   dns_nsupdate_gss (for GSS-TSIG support)
#   dns_virsh (simple implementation for libvirt)
:use_provider: dns_virsh
# use this setting if you want to override default TTL setting (86400)
:dns_ttl: 86400

In the Capsules tab, I see the server correctly configured in the subdomains. 
However, when I try to provision a new host, the DHCP/DNS host is ignored!

The /var/log/foreman-proxy/proxy.log has the following entry:

DHCP virsh provider > error: unable to retrive virsh info: virsh provider error: virsh call > failed (pid 32091 exit 1) - error: failed to connect to the hypervisor error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory

So, from this, I guess that either virsh communication in 6.2.x is limited to a local KVM, or that the server I configured in the installer is ignored. In which case, the installer should, at least, raise a WARNING that this functionality is not implemented. 

Suffice to say, from the foreman-proxy user I can issue virsh commands (like eg sudo virsh qemu://kvmbox.testenv/system list)

Version-Release number of selected component (if applicable):
6.2.4

How reproducible:
100%

Steps to Reproduce:
1. Follow the aforementioned installation

Actual results:
DHCP cannot register the assigned by Satellite IP.

Expected results:
DHCP lease should be recorded in libvirtd. 

Additional info: