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.
Descriptionkuwei@redhat.com
2017-05-03 09:23:21 UTC
Created attachment 1275853[details]
v2v.log
Description of problem:
Failed to convert guest from vmware to kvm by virt-v2v with qemu-img-rhev-2.9.0-2.el7.x86_64
Version-Release number of selected component (if applicable):
qemu-img-rhev-2.9.0-2.el7.x86_64
libvirt-3.2.0-3.el7.x86_64
virt-v2v-1.36.3-3.el7.x86_64
libguestfs-1.36.3-3.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1:Convert a rhel7.3 guest from vmware to kvm,details pls refer to attachment v2vlog
#virt-v2v -ic vpx://root.75.182/data/10.73.3.19/?no_verify=1 esx5.5-rhel7.3-x86_64 --password-file /tmp/passwd -on test
[ 0.0] Opening the source -i libvirt -ic vpx://root.75.182/data/10.73.3.19/?no_verify=1 esx5.5-rhel7.3-x86_64
[ 1.3] Creating an overlay to protect the source from being modified
[ 1.7] Initializing the target -o libvirt -os default
[ 1.7] Opening the overlay
^c
Result: the above conversion can't be finished
Addition info
1.It is works fine below packages it:
qemu-kvm-rhev-2.8.0-6.el7.x86_64
libvirt-3.2.0-3.el7.x86_64
virt-v2v-1.36.3-3.el7.x86_64
libguestfs-1.36.3-3.el7.x86_64
2.A same bug i think :Bug 1430287
Comment 4Richard W.M. Jones
2017-05-03 13:34:12 UTC
I am able to reproduce this with:
* qemu-kvm-rhev-2.9.0-2.el7.x86_64
* Upstream qemu (e619b14746e5d)
Does NOT reproduce with:
* qemu-kvm-rhev-2.8.0-6.el7.x86_64
Also (as kuwei also reported to me on IRC) the file is stuck at 8K in
the download.
So it's an actual bug in upstream qemu.
I'm going to bisect this to see if I can isolate a particular commit.
Comment 5Richard W.M. Jones
2017-05-03 14:54:38 UTC
ba3186c4e473963ba83b5792f3d02d4ac0a76ba5 is the first bad commit
commit ba3186c4e473963ba83b5792f3d02d4ac0a76ba5
Author: Paolo Bonzini <pbonzini>
Date: Wed Feb 22 19:07:23 2017 +0100
curl: do not use aio_context_acquire/release
Now that all bottom halves and callbacks take care of taking the
AioContext lock, we can migrate some users away from it and to a
specific QemuMutex or CoMutex.
Protect BDRVCURLState access with a QemuMutex.
Reviewed-by: Stefan Hajnoczi <stefanha>
Signed-off-by: Paolo Bonzini <pbonzini>
Message-id: 20170222180725.28611-2-pbonzini
Signed-off-by: Stefan Hajnoczi <stefanha>
:040000 040000 1a66f1866953d188bdd51318f470c43f6aedf06e d0f24bf0226fa8cc5d8311d74c5542fa225638ea M block
Reverting this commit fixes the problem.
Comment 6Richard W.M. Jones
2017-05-03 15:43:00 UTC
Result: Pass
# virt-v2v -ic vpx://root.75.182/data/10.73.3.19/?no_verify=1 esx5.5-rhel7.3-x86_64 --password-file /tmp/passwd -on shuang
[ 0.0] Opening the source -i libvirt -ic vpx://root.75.182/data/10.73.3.19/?no_verify=1 esx5.5-rhel7.3-x86_64
[ 1.2] Creating an overlay to protect the source from being modified
[ 1.6] Initializing the target -o libvirt -os default
[ 1.6] Opening the overlay
[ 26.6] Inspecting the overlay
[ 179.2] Checking for sufficient free disk space in the guest
[ 179.2] Estimating space required on target for each disk
[ 179.2] Converting Red Hat Enterprise Linux Server 7.3 (Maipo) to run on KVM
virt-v2v: This guest has virtio drivers installed.
[1615.0] Mapping filesystem data to avoid copying unused and blank areas
[1641.0] Closing the overlay
[1641.2] Checking if the guest needs BIOS or UEFI to boot
[1641.2] Assigning disks to buses
[1641.2] Copying disk 1/1 to /var/lib/libvirt/images/shuang-sda (raw)
(100.00/100%)
[2316.9] Creating output metadata
Pool default refreshed
Domain shuang defined from /tmp/v2vlibvirt7f19ad.xml
Package: qemu-img-rhev-2.9.0-8.el7.x86_64.rpm
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://access.redhat.com/errata/RHSA-2017:2392