Hey Daniel,<div><br></div><div>Sorry, I should have mentioned that. Yes, I did setup the x509/TLS certificates based on the instructions provided by the libvirt documentation. The setup with the certificates work flawlessly with 0.4.6. Here is a successful run of the virsh command using libvirt 0.4.6 with the certificates:</div> <div><br></div><div><div># LIBVIRT_DEBUG=6 virsh -d 5 -c xen://node3/ list</div><div>command: "list "</div><div>DEBUG: libvirt.c: virInitialize (register drivers)</div><div>DEBUG: xen_internal.c: xenHypervisorInit (Using new hypervisor call: 30003</div> <div>)</div><div>DEBUG: xen_internal.c: xenHypervisorInit (Using hypervisor call v2, sys ver6 dom ver5</div><div>)</div><div>DEBUG: libvirt.c: virConnectOpenAuth (name=xen://node3/, auth=0x675b9c, flags=0)</div><div>DEBUG: libvirt.c: do_open (name "xen://node3/" to URI components:</div> <div> scheme xen</div><div> opaque (null)</div><div> authority (null)</div><div> server node3</div><div> user (null)</div><div> port 0</div><div> path /</div><div>)</div><div>DEBUG: libvirt.c: do_open (trying driver 0 (Test) ...)</div> <div>DEBUG: libvirt.c: do_open (driver 0 Test returned DECLINED)</div><div>DEBUG: libvirt.c: do_open (trying driver 1 (QEMU) ...)</div><div>DEBUG: libvirt.c: do_open (driver 1 QEMU returned DECLINED)</div><div>DEBUG: libvirt.c: do_open (trying driver 2 (Xen) ...)</div> <div>DEBUG: libvirt.c: do_open (driver 2 Xen returned DECLINED)</div><div>DEBUG: libvirt.c: do_open (trying driver 3 (remote) ...)</div><div>DEBUG: remote_internal.c: doRemoteOpen (proceeding with name = xen:///)</div><div> DEBUG: remote_internal.c: initialise_gnutls (loading CA file /etc/pki/CA/cacert.pem)</div><div>DEBUG: remote_internal.c: initialise_gnutls (loading client cert and key from files /etc/pki/libvirt/clientcert.pem and /etc/pki/libvirt/private/clientkey.pem)</div> <div>DEBUG: libvirt.c: do_open (driver 3 remote returned SUCCESS)</div><div>DEBUG: libvirt.c: do_open (network driver 0 Test returned DECLINED)</div><div>DEBUG: libvirt.c: do_open (network driver 1 QEMU returned DECLINED)</div> <div>DEBUG: libvirt.c: do_open (network driver 2 remote returned SUCCESS)</div><div>DEBUG: libvirt.c: do_open (storage driver 0 Test returned DECLINED)</div><div>DEBUG: libvirt.c: do_open (storage driver 1 storage returned DECLINED)</div> <div>DEBUG: libvirt.c: do_open (storage driver 2 remote returned SUCCESS)</div><div>DEBUG: libvirt.c: virConnectNumOfDomains (conn=0x8e681f0)</div><div>DEBUG: libvirt.c: virConnectListDomains (conn=0x8e681f0, ids=0x8e76f58, maxids=1)</div> <div> Id Name State</div><div>----------------------------------</div><div>DEBUG: libvirt.c: virDomainLookupByID (conn=0x8e681f0, id=0)</div><div>DEBUG: hash.c: __virGetDomain (New hash entry 0x8e8e330)</div> <div>DEBUG: libvirt.c: virDomainGetInfo (domain=0x8e8e330, info=0xbfce7cc4)</div><div>DEBUG: libvirt.c: virDomainGetName (domain=0x8e8e330)</div><div>DEBUG: libvirt.c: virDomainGetID (domain=0x8e8e330)</div><div> 0 Domain-0 running</div> <div>DEBUG: libvirt.c: virDomainFree (domain=0x8e8e330)</div><div>DEBUG: hash.c: virUnrefDomain (unref domain 0x8e8e330 Domain-0 1)</div><div>DEBUG: hash.c: virReleaseDomain (release domain 0x8e8e330 Domain-0)</div><div>DEBUG: hash.c: virReleaseDomain (unref connection 0x8e681f0 xen://node3/ 2)</div> <div><br></div><div>DEBUG: libvirt.c: virConnectClose (conn=0x8e681f0)</div><div>DEBUG: hash.c: virUnrefConnect (unref connection 0x8e681f0 xen://node3/ 1)</div><div>DEBUG: hash.c: virReleaseConnect (release connection 0x8e681f0 xen://node3/)</div> </div><div><br></div><div>Hany<br><br><div class="gmail_quote">On Mon, Jun 8, 2009 at 12:34 PM, Daniel P. Berrange <span dir="ltr"><<a href="mailto:berrange@redhat.com">berrange@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="im">On Mon, Jun 08, 2009 at 12:20:12PM -0400, Hany Fahim wrote:<br> > Hey Daniel,<br> > Thanks for the reply. The strange thing is, libvirt isn't even attempting to<br> > establish a connection with the remote server. I've performed tcpdumps to<br> > verify this; no traffic is exchanged between the two hosts when executing<br> > the virsh command. If I switch back to a version of libvirt below 0.5.0 such<br> > as 0.4.6, it works like a charm.<br> <br> </div>Have you configured the neccessary x509/TLS certificates on the client side ?<br> <div><div></div><div class="h5"><br> Daniel<br> --<br> |: Red Hat, Engineering, London -o- <a href="http://people.redhat.com/berrange/" target="_blank">http://people.redhat.com/berrange/</a> :|<br> |: <a href="http://libvirt.org" target="_blank">http://libvirt.org</a> -o- <a href="http://virt-manager.org" target="_blank">http://virt-manager.org</a> -o- <a href="http://ovirt.org" target="_blank">http://ovirt.org</a> :|<br> |: <a href="http://autobuild.org" target="_blank">http://autobuild.org</a> -o- <a href="http://search.cpan.org/~danberr/" target="_blank">http://search.cpan.org/~danberr/</a> :|<br> |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|<br> </div></div></blockquote></div><br></div>