Red Hat Bugzilla – Bug 955575
libvirt does not support virtualHW.version 9
Last modified: 2013-11-21 03:59:16 EST
+++ 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
I can reproduce this issue. version: virt-v2v-0.8.9-2.el6.x86_64 libvirt-0.10.2-18.el6_4.4.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
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@redhat.com> Date: Tue Apr 30 14:46:54 2013 +0200 esx: Support virtualHW version 9
We decided not to rebase libvirt in RHEL 6.5 to avoid stability issues we faced in 6.4. This bug has already been trivially fixed upstream but it is not considered important enough to be backported to RHEL 6.5. Thus I'm pushing this bug to RHEL 6.6 (and setting Upstream keyword to indicate we have patches upstream) for now. If you don't agree with this resolution, please, give us reasons which you think are strong enough for us to reevaluate the decision not to backport patches for this bug.
Come on, this is like a 4 line patch, and it *IS* very important for virt-v2v users. We have had several who have his this bug.
Oops, sorry about that Rich. This bug slipped from the important (and trivial) list into the trivial and unimportant list. I'm moving it back to 6.5.
Tested the bug with: libvirt-0.10.2-19.el6.x86_64 virt-v2v-0.9.1-1.el6_5.x86_64 Steps: 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 esx5.0-rhel6.2-x86_64_esx5.0-rhel6.2-x86_64: 100% [====================================================]D 0h03m46s virt-v2v: WARNING: No mapping found for bridge interface VM Network in config file. The converted guest may not start until its network interface is updated. virt-v2v: esx5.1-rhel6-vmx9 configured with virtio drivers. Refer to above comments,move the bug as 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. http://rhn.redhat.com/errata/RHBA-2013-1581.html