Comment 7 for bug 1576688

I've checked Aleksey's environment and see that libvirtd *does not* listen on a TCP socket at all:

http://paste.openstack.org/show/496057/

At the same time *it is* configured to listen for TCP connections in /etc/libvirt/libvirtd.conf and /etc/default/libvirtd:

root@node-2:~# cat /etc/default/libvirtd
# Defaults for libvirtd initscript (/etc/init.d/libvirtd)
# This is a POSIX shell fragment

# Start libvirtd to handle qemu/kvm:
start_libvirtd="yes"

# options passed to libvirtd, add "-l" to listen on tcp
libvirtd_opts="-d -l"

# pass in location of kerberos keytab
#export KRB5_KTNAME=/etc/libvirt/libvirt.keytab

# Whether to mount a systemd like cgroup layout (only
# useful when not running systemd)
#mount_cgroups=yes
# Which cgroups to mount
#cgroups="memory devices"

root@node-2:~# cat /etc/libvirt/libvirtd.conf | grep listen
# Flag listening for secure TLS connections on the public TCP/IP port.
# NB, must pass the --listen flag to the libvirtd process for this to
listen_tls = 0
# NB, must pass the --listen flag to the libvirtd process for this to
listen_tcp = 1
#listen_addr = "192.168.0.1"

Based on the ps output, -l and -d options were ignored on start. Neither -f (config file path) was passed to libvirtd. So it runs with default settings.

My current understanding is that https://review.fuel-infra.org/gitweb?p=packages/trusty/libvirt.git;a=commit;h=b109ae4033b0eb02adfee7c55d163081975e7551 changed the way how libvirtd is started and options specified in /etc/default/libvirtd are ignored, /etc/libvirt/libvirtd.conf is not passed to libvirtd executable on start.

MOS Linux team, please take a look at this. Our puppet manifests specifically configure libvirtd to start with -l (listen) and -d (daemon) options.