Guillaume Rousse wrote:
Daniel P. Berrange a écrit :The daemon libvirtd will always listen for UNIX socket connections. You have to explicitly turn on TCP support, after having setup certificates. If using SSH, then we simply tunnel to the UNIX socket over SSH so all you need do is start the libvirtd daemon on the remote host.Can you rephrase the documentation a little bit then ? It seems to imply you have to do some additional libvirtd configuration for ssh transport usage.
Suggested change to the documentation attached.
Also, from where does those error and warning come ? [root acacia ~]# LC_ALL=C virsh -c xen:/// list libvir: Remote error : No such file or directory libvir: warning : Failed to find the network: Is the daemon running ?That is a sign that the libvirtd daemon is notrunning on the host in questions.
Well sometimes, but also it can be a sign that virsh is trying to use the wrong Unix socket, or that the Unix socket has the wrong permissions or is otherwise inaccessible. Try:
/usr/sbin/libvirtd --help (which should print out all the paths expected by libvirtd) and: strace virsh -c xen:/// list which should tell you what socket virsh is trying to connect on.In any case this warning can be ignored unless you want to manipulate networks.
Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903
Index: docs/libvir.html =================================================================== RCS file: /data/cvs/libvirt/docs/libvir.html,v retrieving revision 1.85 diff -u -r1.85 libvir.html --- docs/libvir.html 21 Sep 2007 20:17:09 -0000 1.85 +++ docs/libvir.html 27 Sep 2007 09:37:50 -0000 @@ -1590,8 +1590,8 @@ <a href="http://www.openssh.com/" title="OpenSSH homepage">ssh (secure shell)</a> connection. Requires <a href="http://netcat.sourceforge.net/">Netcat (nc)</a> - installed on the remote machine, and the remote libvirtd should - be listening on the unix transport. You should use some sort of + installed and libvirtd should be running + on the remote machine. You should use some sort of ssh key management (eg. <a href="http://mah.everybody.org/docs/ssh" title="Using ssh-agent with ssh">ssh-agent</a>)
Description: S/MIME Cryptographic Signature