On Mon, Dec 13, 2010 at 02:29:43PM +0100, Matthias Bolte wrote:
2010/12/12 Justin Clift <jclift@redhat.com>:
Hi Matthias (and anyone else interested),
Just added a win32 installation package to the website, for libvirt 0.8.6.
http://libvirt.org/sources/win32_experimental/Libvirt-0.8.6-0.exe
This has the libcurl stuff in it you put together, so (in theory) it should connect to remote vSphere/ESX servers.
Do you (or anyone) have time to try it out against vSphere/ESX/similar?
Going to update the Windows page on the website pointing to it, when we know it's working ok. :)
Regards and best wishes,
Justin Clift
I tested it and it works with ESX and QEMU over TLS. Here are some comments:
1) I wonder why you never pushed this patch: https://www.redhat.com/archives/libvir-list/2010-November/msg00761.html
2) libcurl license is missing in the installer.
3) There is no readme.txt about where to put TLS certs to make qemu+tls:// work.
4) The installer remembers the install location. Therefore, it suggest to install in the same location as the previous installer for libvirt 0.8.5. But it doesn't check if a previous version is already installed and doesn't suggest to uninstall it first. This results in libvirt 0.8.6 being installed over 0.8.5. The installer overwrites existing files without notice.
This raises the question of how the tools depending on libvirt will be distributed. eg virt-viewer. If they're separate, then we need to make sure the tools continue working, after any update of libvirt without changing paths manually. IMHO, rather than just distributing a libvirt installer, we should distribute a 'virt tools' installer on virt-tools.org which has a complete bundle of everything that has been ported to Win32, libvirt core, language bindings and apps. The installer would of course allow you to pick & choose which bits to install. Regards, Daniel