Comment 3 for bug 1676208

Apologies for creating confusion. It is kind of complicated setup :) It is docker containers environment. Everything runs on the same physical host. libvirtd runs inside of a docker container and is fine (it is part of kola-kubernetes openstack). What I need to do it and the same works with centos, is to define VM manually on the host and then be able to start it. I would like to use the socket and PID of already existing libvirtd process running inside of a docker container. Since libvirtd container runs in the same namespace as the host, both host and container share the same PID namespaces and network namespaces.
I cannot run any virsh commands as every time it fails to connect to the hypervisor. On the next run I will collect dpkg output you requested. Please let me know if you need further clarification.