Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
The bug can be also reproduced on rhel6,so cloned it.
+++ This bug was initially created as a clone of Bug #1213345 +++
Description of problem:
Virsh support connect esxi 6.0 hypervisor.
Version-Release number of selected component (if applicable):
libvirt-1.2.8-16.el7.x86_64
How reproducible:
100%.
Steps to Reproduce:
1.Prepare esxi 6.0 server.
2.Use virsh to connect the server,error shows.
# virsh -c esx://root.72.49/?no_verify=1
Enter root's password for 10.66.72.49:
error: failed to connect to the hypervisor
error: internal error: Expecting VI API major/minor version '2.5', '4.x' or '5.x' but found '6.0'
Actual results:
As description.
Expected results:
Virsh support connect esxi 6.0 hypervisor.
Additional info:
Tested with:
libvirt-0.10.2-56.el6.x86_64
Steps:
1.Use virsh to connect esxi 6.0 server.
# virsh -c esx://10.66.144.40/?no_verify=1
Enter username for 10.66.144.40 [root]:
Enter root's password for 10.66.144.40:
Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands
'quit' to quit
virsh # list --all
Id Name State
----------------------------------------------------
1 win2012R2-vcenter running
33 iscsi-test running
43 VMware-vcenter-server-app running
- app_vcenter600 shut off
- Auto-esx6.0-win7-efi shut off
- bug1260689-win2008R2-GPO-Macfee shut off
- esx6.0-rhel5.11-i386 shut off
- esx6.0-rhel5.11-x86_64 shut off
- esx6.0-rhel6.7-i386 shut off
2.Use virsh to connect esxi 6.0 server via vcenter 6.0:
# virsh -c vpx://root.145.47/data/10.66.144.40/?no_verify=1
Enter root's password for 10.66.145.47:
Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands
'quit' to quit
virsh # list --all
Id Name State
----------------------------------------------------
62 win2012R2-vcenter running
88 VMware-vcenter-server-app running
- app_vcenter600 shut off
- Auto-esx6.0-win7-efi shut off
- bug1260689-win2008R2-GPO-Macfee shut off
- esx6.0-rhel5.11-i386 shut off
- esx6.0-rhel5.11-x86_64 shut off
Both of the above virsh command works fine,so move the bug to VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-0738.html