2013/8/3 varun bhatnagar <varun292006(a)gmail.com>
Thanks a ton for the reply Matthias. I tried your suggestion but now I got one more
message saying:
virsh # connect esx://172.16.73.14/?no_verify=1
Enter username for 172.16.73.14 [root]: root
Enter root's password for 172.16.73.14:
error: Failed to connect to the hypervisor
error: internal error: curl_easy_perform() returned an error: Unsupported protocol (1) :
Protocol https not supported or disabled in libcurl
Is it because of the curl package? I thought of building curl with https support but
there was no such option (--with-https). Can you please tell me why am I getting this.
Yes, this is because your libcurl was build without SSL support. You
need to enable an SSL backend when you build libcurl. libcurl support
several SSL libraries, see
http://curl.haxx.se/docs/ssl-compared.html
There is a configure option for every single one of this SSL
libraries. I've been using GnuTLS, the configure option for this one
is --with-gnutls.
On Thu, Aug 1, 2013 at 9:09 PM, Matthias Bolte
<matthias.bolte(a)googlemail.com> wrote:
>
> 2013/8/1 varun bhatnagar <varun292006(a)gmail.com>:
> > Hi,
> >
> > I was trying to connect to ESX server using libvirt's virsh console but I
am
> > getting the following error:
> >
> > virsh# connect esx://172.16.73.14
> > Enter username for 172.16.73.14 [root]: root
> > Enter root's password for 172.16.73.14:
> > error: Failed to connect to the hypervisor
> > error: internal error curl_easy_perform() returned an error: Peer
> > certificate cannot be authenticated with known CA certificates (60) : SSL
> > certificate problem, verify that the CA cert is OK. Details:
> > error: 14090086:SSL routine:SSL3_GET_SERVER_CERTIFICATE:certificate verify
> > failed.
> >
> > Can anyone please help me out with this one and tell me how to resolve this
> > error?
>
> See
http://libvirt.org/drvesx.html#certificates
>
> By default an ESX server uses self-signed SSL certificates. You either
> need to tell libvirt to not verify the certificates (virsh connect
> esx://172.16.73.14/?no_verify=1) or replace the SSL certificates with
> offically signed ones.
>
> --
> Matthias Bolte
>
http://photron.blogspot.com
--
Matthias Bolte
http://photron.blogspot.com