You may want to look in the qemu log of the vm to see if there's something deeper going on, perhaps the qemu process is not fully starting due to some other issue. /var/log/libvirt/qemu/v-1-VM.log, or something like that.
On Sun, Apr 20, 2014 at 11:22 PM, Marcus <shadow...@gmail.com> wrote: > No, it has nothing to do with ssh or libvirt daemon. It's the literal > unix socket that is created for virtio-serial communication when the > qemu process starts. The question is why the system is refusing access > to the socket. I assume this is being attempted as root. > > On Sat, Apr 19, 2014 at 9:58 AM, Nux! <n...@li.nux.ro> wrote: >> On 19.04.2014 15:24, Giri Prasad wrote: >> >>> >>> # grep listen_ /etc/libvirt/libvirtd.conf >>> listen_tls=0 >>> listen_tcp=1 >>> #listen_addr = "192.XX.XX.X" >>> listen_addr = "0.0.0.0" >>> >>> # >>> /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl >>> -n v-1-VM -p >>> >>> %template=domP%type=consoleproxy%host=192.XXX.XX.5%port=8250%name=v-1-VM%zone=1%pod=1%guid=Proxy.1%proxy_vm=1%disable_rp_filter=true%eth2ip=192.XXX.XX.173%eth2mask=255.255.255.0%gateway=192.XXX.XX.1%eth0ip=169.254.0.173%eth0mask=255.255.0.0%eth1ip=192.XXX.XX.166%eth1mask=255.255.255.0%mgmtcidr=192.XXX.XX.0/24%localgw=192.XXX.XX.1%internaldns1=192.XXX.XX.1%dns1=192.XXX.XX.1 >>> . >>> ERROR: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent - >>> Connection refused >> >> >> Do you have "-l" or "--listen" as LIBVIRTD_ARGS in /etc/sysconfig/libvirtd? >> >> (kind of stabbing in the dark) >> >> >> -- >> Sent from the Delta quadrant using Borg technology! >> >> Nux! >> www.nux.ro
