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.

+++ This bug was initially created as a clone of Bug #929354 +++

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible: Very



Steps to Reproduce:
1. Try to import a VM from an esx host that has hardware version 9 using virt-v2v
2. 
3.
  
Actual results: libvirt responds with virtualHW.version 9 not supported


Expected results: VM is imported


Additional info:

--- Additional comment from Dan Kozlowski on 2013-03-29 20:05:42 EDT ---

This is not a virt-v2v bug, that is just the tool I used to trigger it. The offending lines are 1307 and 1308 of src/vmx/vmx.c

Patch proposed upstream:

http://www.redhat.com/archives/libvir-list/2013-April/msg02137.html

Ignore previous message, the proposal is in this one:

http://www.redhat.com/archives/libvir-list/2013-April/msg02131.html

Moving to POST:

commit e0eb672e0046af365a4039cc68311e5d844fc7bf
Author: Martin Kletzander <mkletzan>
Date:   Tue Apr 30 14:46:54 2013 +0200

    esx: Support virtualHW version 9

I can reproduce this issue.
version:
libvirt-1.0.3-1.el7.x86_64
virt-v2v-0.9.0-2.el7.x86_64

1.Update a guest to hardware version 9 on esx5.1.

2.Use virt-v2v to convert the guest.
# virt-v2v -ic esx://10.66.6.211/?no_verify=1 -os default esx5.1-rhel6-vmx9
libvirt error code: 1, message: internal error Expecting VMX entry 'virtualHW.version' to be 4, 7 or 8 but found 9

Tested with:
libvirt-1.0.5-1.el7.x86_64
virt-v2v-0.9.0-2.el7.x86_64

Repeat the above steps,there is no such error from libvirt,so move the bug to VERIFIED.
# virt-v2v -ic esx://10.66.6.211/?no_verify=1 -os default esx5.1-rhel6-vmx9
esx5.0-rhel6.2-x86_64_esx5.0-rhel6.2-x86_64:  47% [=================*=================                 ]0m59s Left

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.