Yep, that did it. It works when using xen+tls as the transport. Thanks for your help Daniel.<div><br></div><div>Hany<br><br><div class="gmail_quote">On Mon, Jun 8, 2009 at 12:53 PM, Daniel P. Berrange <span dir="ltr">&lt;<a href="mailto:berrange@redhat.com">berrange@redhat.com</a>&gt;</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:47:30PM -0400, Hany Fahim wrote:<br>
&gt; Hey Daniel,<br>
</div><div class="im">&gt; Sorry, I should have mentioned that. Yes, I did setup the x509/TLS<br>
&gt; certificates based on the instructions provided by the libvirt<br>
&gt; documentation. The setup with the certificates work flawlessly with 0.4.6.<br>
&gt; Here is a successful run of the virsh command using libvirt 0.4.6 with the<br>
&gt; certificates:<br>
&gt;<br>
&gt; # LIBVIRT_DEBUG=6 virsh -d 5 -c xen://node3/ list<br>
<br>
</div>I think i have a spotted a possible bug here. Try using an explicit<br>
transport scheme in the URI , eg  xen+tls://node3/  Looks like we<br>
may have broken the implicit TLS support<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>