Hey Daniel, Thanks for the reply. The strange thing is, libvirt isn't even attempting to establish a connection with the remote server. I've performed tcpdumps to verify this; no traffic is exchanged between the two hosts when executing the virsh command. If I switch back to a version of libvirt below 0.5.0 such as 0.4.6, it works like a charm.
Is there anything else I could try? Hany On Mon, Jun 8, 2009 at 7:04 AM, Daniel P. Berrange <berra...@redhat.com>wrote: > On Sun, Jun 07, 2009 at 02:02:20PM -0400, Hany Fahim wrote: > > Hi, > > I'm currently running a few servers with CentOS 5.3 (i386) with the stock > > Xen version: > > > > # rpm -q kernel-xen xen libvirt > > kernel-xen-2.6.18-92.1.22.el5 > > kernel-xen-2.6.18-128.1.6.el5 > > xen-3.0.3-80.el5_3.2 > > libvirt-0.6.3-1 > > > > libvirt was compiled from the src RPM from libvirt.org to run on i386 > > architecture without issue. I'm having a problem when trying to connect > to > > remote Xen installations using versions of libvirt starting from 0.5.0 > and > > above. When issuing virsh commands to query the local instance, it works > > without issue, but any remote sources gives 'error: failed to connect to > the > > hypervisor'. Here's what LIBVIRT_DEBUG reveals: > > > > # LIBVIRT_DEBUG=6 virsh -d 5 -c xen://node3/ list > > command: "list " > > 13:53:17.133: debug : do_open:930 : trying driver 0 (Test) ... > > 13:53:17.133: debug : do_open:936 : driver 0 Test returned DECLINED > > 13:53:17.133: debug : do_open:930 : trying driver 1 (Xen) ... > > 13:53:17.133: debug : do_open:936 : driver 1 Xen returned DECLINED > > 13:53:17.133: debug : do_open:930 : trying driver 2 (OPENVZ) ... > > 13:53:17.133: debug : do_open:936 : driver 2 OPENVZ returned DECLINED > > 13:53:17.133: debug : do_open:930 : trying driver 3 (VBOX) ... > > 13:53:17.133: debug : do_open:936 : driver 3 VBOX returned DECLINED > > 13:53:17.133: debug : do_open:930 : trying driver 4 (remote) ... > > 13:53:17.133: debug : do_open:936 : driver 4 remote returned DECLINED > > 13:53:17.133: debug : virUnrefConnect:210 : unref connection 0x93275d0 1 > > 13:53:17.134: debug : virReleaseConnect:171 : release connection > 0x93275d0 > > error: failed to connect to the hypervisor > > > It looks very much like the remote driver is failing to connect to the > remote > libvirtd daemon. Please verify that libvirtd on the remote host was started > with the --listen flag, and that you have configured x509 certificates and > have not disabled the 'listen_tls' config param in > /etc/libvirt/libvirtd.conf > > > Daniel > -- > |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/:| > |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org:| > |: http://autobuild.org -o- http://search.cpan.org/~danberr/:| > |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 > :| >
-- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list