[libvirt] Problem connecting to hypervisor.
I am trying to establish a connection (using virsh command) to a couple of hypervisor hosts, both on SLES 11.3 environments. The host from where i am making both the connections is a SLES 10.4 instance. *kvmh911351246:~ # virsh -c qemu+ssh://9.113.51.247:22/system <http://9.113.51.247:22/system>libvir: XML-RPC error : authentication requirederror: failed to connect to the hypervisor* The SSH authentication to hypervisor host 9.113.51.247 has already been established. *kvmh911351246:~ # ssh root@9.113.51.247 <root@9.113.51.247>Last login: Tue Jun 3 11:31:56 2014 from scm-kvmh2-rhel6 SLES11-51-247:~ #* Hence the cause of the authentication failure is not clear. The second connection to another SLES 11.3 host looks like *virsh # connect qemu+ssh://9.121.58.19:22/system <http://9.121.58.19:22/system> bash: socat: command not foundlibvir: Remote error : socket closed unexpectedlyerror: Failed to connect to the hypervisor* where the cause of the error is entirely different. The libvirt packages available on these environments are *9.113.51.247 (SLES 11.3)* *libvirt-cim-0.5.12-0.7.16libvirt-1.0.5.1-0.7.10libvirt-python-1.0.5.1-0.7.10libvirt-client-32bit-1.0.5.1-0.7.10 libvirt-lock-sanlock-1.0.5.1-0.7.10libvirt-client-1.0.5.1-0.7.10* *9.121.58.19 (SLES 11.3)* *libvirt-cim-0.5.12-0.7.16libvirt-client-1.0.5.1-0.7.10libvirt-python-1.0.5.1-0.7.10 libvirt-1.0.5.1-0.7.10* *9.113.51.246 ( SLES 10.4)* *libvirt-python-0.3.3-18.22.1libvirt-devel-0.3.3-18.22.1libvirt-0.3.3-18.22.1* How can these connection failures be debugged? Is there a way to know more information about them?
Vikas Kokare wrote:
I am trying to establish a connection (using virsh command) to a couple of hypervisor hosts, both on SLES 11.3 environments. The host from where i am making both the connections is a SLES 10.4 instance.
Hi Vikas, FYI, this list is for discussing upstream libvirt development, not a forum for distro support. Since you are using SLES, it would be best to enter a support ticket with SUSE.
/kvmh911351246:~ # virsh -c qemu+ssh://9.113.51.247:22/system <http://9.113.51.247:22/system> libvir: XML-RPC error : *authentication required* error: failed to connect to the hypervisor/ / / The SSH authentication to hypervisor host 9.113.51.247 has already been established.
/kvmh911351246:~ # *ssh root@9.113.51.247 <mailto:root@9.113.51.247>* Last login: Tue Jun 3 11:31:56 2014 from scm-kvmh2-rhel6 SLES11-51-247:~ #/ / / Hence the cause of the authentication failure is not clear.
The second connection to another SLES 11.3 host looks like / virsh # connect qemu+ssh://9.121.58.19:22/system <http://9.121.58.19:22/system> *bash: socat: command not found libvir: Remote error : socket closed unexpectedly *error: Failed to connect to the hypervisor/
You could try installing socat on the SLES11 SP3 systems.
where the cause of the error is entirely different.
The libvirt packages available on these environments are
*9.113.51.247 (SLES 11.3)* /libvirt-cim-0.5.12-0.7.16 libvirt-1.0.5.1-0.7.10 libvirt-python-1.0.5.1-0.7.10 libvirt-client-32bit-1.0.5.1-0.7.10 libvirt-lock-sanlock-1.0.5.1-0.7.10 libvirt-client-1.0.5.1-0.7.10/
*9.121.58.19 (SLES 11.3)* /libvirt-cim-0.5.12-0.7.16 libvirt-client-1.0.5.1-0.7.10 libvirt-python-1.0.5.1-0.7.10 libvirt-1.0.5.1-0.7.10/
The libvirt packages on your SLES11 SP3 machines are quite old and need updated. Regards, Jim
participants (2)
-
Jim Fehlig -
Vikas Kokare