I've added this info to the documentation so other people can benefit from it.
Thanks
On Fri, Apr 27, 2012 at 5:15 PM, Nicolas Diogo nicolasdi...@gmx.com wrote:
they i have things - working around the TLS messages on the syslog was
to set
on /etc/libvirt/libvirtd.conf
listen_tls = 0
it
Do you have that problem only when live migrating or for all the commands?
QEMU_PROTOCOL variable is only used for live migrations as it is
needed to connect to the remote machine. The rest of the commands use
unix sockets so TLS should not be a problem. Are unix sockets enabled
in your libvirt
Sorry for bumping this.
but i am just trying to ensure that i understand this requirement of ON
correctly
we have to setup TLS and SSH for all the hosts running KVM?
thanks,
Nicolas
On 25/04/12 18:13, Nicolas Diogo wrote:
hi,
i have found another discussion on the list:
they i have things - working around the TLS messages on the syslog was
to set
on /etc/libvirt/libvirtd.conf
listen_tls = 0
it works find. but i would like to find out if others had run into the
same problem.
so it seems that i am not alone
thanks Luis
On 27/04/12 15:26, Luis Ramon Lopez
hi,
i have found another discussion on the list:
http://lists.opennebula.org/htdig.cgi/users-opennebula.org/2011-April/005013.html
and while following the documentation:
http://opennebula.org/documentation:archives:rel2.0:kvmg
i have come across the same problem.
when starting libvirt-bin, it
