...

Hi, I'm the package maintainer of libvirt for the Pardus distribution. While trying to update the package to the latest 0.7.0, I recognized that configure script does not find libssh.

I checked our system and found out that we are using libssh2 instead of libssh.

...

From this website (http://www.libssh2.org/libssh2-vs-libssh.html),

---------- Forwarded message ---------- From: Daniel Veillard <veillard@redhat.com> To: Emre Erenoglu <erenoglu@gmail.com> Date: Thu, 20 Aug 2009 11:14:53 +0200 Subject: Re: [libvirt] libvirt with libssh2? On Thu, Aug 20, 2009 at 10:50:37AM +0200, Emre Erenoglu wrote: libssh2

...

developers summarize their differences.

My questions: 1) Is there a specific reason why we are using libssh? Is there a patch to make libvirt use libssh2 instead? 2) What functionality do we loose if we don't have libssh in the system? (depending on this, I'll also package libssh or not)

I guess you activated --with-phyp which currently requires libssh, but this will be fixed in the future, the result is just that that driver gets desactivated for now if you don't have libssh

see http://www.mail-archive.com/libvir-list@redhat.com/msg15086.html

Thanks Daniel. I'm a bit foreign to this "Power Hypervisor" thing, but if I'm not wrong from the information that I got from this site: http://publib.boulder.ibm.com/infocenter/systems/scope/hw/index.jsp?topic=/i... than it's nothing that we support in Pardus at the moment. In fact, we only support KVM in our libvirt at the moment, possibly virtualbox in the future. In this case, I'm disabling this pyhp as well as the libssh dependency. Thanks a lot for the info and let me know if my understanding is wrong :) -- Emre