Another strange thing. I tried, in order to solve this, to put my hostname as listening address. I started with the ip, 192.168.2.2, and it works. I then decided to use the domain name, pasquale-Dell, but the socket is not created. Looking into logs it seems it tries to resolve the name, without success. After a lot of tries it just decides to give up. However, in file /etc/hosts the resolution is correctly set and I can just think that libvirt starts before the name discovery system is actually up. The fact the daemon is not started at all confirms this. But now here's the moment I begin to HATE libvirt. You would expect that executing service libvirt-bin start (or restart) would solve this, right? Well, if I do that the deamon correctly starts...but libvirt hangs!! Every connect I try with virsh, let it be local or remote, just hangs indefinitely. The is no *censored* way to restart the libvirt daemon: it just leads to hang. The only *censored* way to restart it is to restart the whole system and pray libvirt starts after the name resolution. 2014-03-07 10:26 GMT+01:00 Pasquale Dir <phate867@gmail.com>:
netstat -lptu gives me tcp6 0 0 [::]:16514 [::]:* LISTEN 1314/libvirtd
so the server is correctly listening on interfaces.
My /etc/libvirt/libvirtd settings are defaulted. My /etc/default/libvirt-bin has "-d -l" options so server is listening.
If I do virsh -c qemu://143.225.229.190/system (that is my ip or an ip belonging to my network) I get "connection refused".
How come? And note that if I put my address, 143.225.229.190, as listening address in the libvirtd conf file, I get "this address class is not supported".