Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 593934 - virsh can't connect to esx server with the no_verify option setted
Summary: virsh can't connect to esx server with the no_verify option setted
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: libvirt
Version: 5.7
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Daniel Veillard
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-20 04:35 UTC by Wayne Sun
Modified: 2010-05-20 08:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-20 08:31:20 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Wayne Sun 2010-05-20 04:35:34 UTC
Description of problem:
virsh -c can't connect to esx hypervisor. The no_verify option was used and set to 1, but error still poped out for not find CA certificate.
 
The error msg:
#virsh -c esx://10.66.65.108/?no_verify=1 dumpxml ESX4.0-RHEL5.4-x86_64
error: Cannot access CA certificate '/etc/pki/CA/cacert.pem': No such file or directory
error: failed to connect to the hypervisor

I've set the .netrc file to store the user and pwd info and can direct log in to esx server.

Version-Release number of selected component (if applicable):
libvirt-0.6.3-33.el5

How reproducible:
always

Steps to Reproduce:
1.virsh -c esx://10.66.65.108/?no_verify=1
2.
3.
  
Actual results:
Failed to connect.

Expected results:
Connect to esx hypervisor successfully.

Additional info:

Comment 1 Matthew Booth 2010-05-20 08:31:20 UTC
Wayne,

I gave you a bum steer on this one. virsh in RHEL 5 isn't linked against v2v-libvirt, so it's too old to have ESX support. You can't get the information I requested from a RHEL 5 box. I'll close this, and we can move back to the virt-v2v bug.


Note You need to log in before you can comment on or make changes to this bug.