On Wed, Nov 17, 2010 at 02:53:15PM +0100, Matthias Bolte wrote: > 2010/11/17 Justin Clift <jclift@xxxxxxxxxx>: > > Also added an additional menu placement for the windows page, in > > order to attract further potential testers. > > --- > > > + Â Â Â<li> > > + Â Â Â ÂThe working connection types at the moment are very limited. ÂOnly > > + Â Â Â Â<b>qemu+tcp://</b> is known to work for sure. ÂAnything using SSH, > > + Â Â Â Âsuch as <b>qemu+ssh://</b>, definitely doesn't work. ÂConnecting > > + Â Â Â Âto ESX servers doesn't yet work either, due to a bug involving > > + Â Â Â ÂGnuTLS, which should be fixed in the next release. > > + Â Â Â</li> > > Don't blame GnuTLS here. As stated on IRC my initial assumption was > wrong. The problem is probably not in GnuTLS, as gnutls-cli works > fine. The problem is in the way libcurl and GnuTLS interact. Therefore > libvirt's GnuTLS usage is not affected, only libcurl's. Also this is mixing up two different drivers, the remote driver vs the ESX driver. The remote driver with TLS should in fact work, and is indeed the *only* transport for the driver which we can recommend using from Windows clients. qemu+tcp:// should not be recommended, because there is no SASL support yet and no one wants to be using this unencrypted with no auth. Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.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@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list