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.
Description of problem:
While converting VMware VMs to RHV, the user is observing low speed. Some of the operations below are taking a huge time which is causing the delay in the conversion.
The generation of new initramfs image took 15+ minutes.
===
[ 1449.362481] dracut[1457] Executing: /sbin/dracut --verbose --add-drivers "virtio virtio_ring virtio_blk virtio_scsi virtio_net virtio_pci" /boot/initramfs-3.10.0-1062.18.1.el7.x86_64.img 3.10.0-1062.18.1.el7.x86_64^M
*** Creating initramfs image file '/boot/initramfs-3.10.0-1062.18.1.el7.x86_64.img' done ***^M
[ 2406.482080] dracut[1457] *** Creating initramfs image file '/boot/initramfs-3.10.0-1062.18.1.el7.x86_64.img' done ***^M
commandrvf: stdout=n stderr=n flags=0x0^M
commandrvf: umount /sysroot/sys^M
commandrvf: stdout=n stderr=n flags=0x0^M
commandrvf: umount /sysroot/proc^M
commandrvf: stdout=n stderr=n flags=0x0^M
commandrvf: umount /sysroot/dev/pts^M
commandrvf: stdout=n stderr=n flags=0x0^M
commandrvf: umount /sysroot/dev^M
renaming /sysroot/etc/6k7w5pmk to /sysroot/etc/resolv.conf^M
guestfsd: => command (0x32) took 1046.94 secs^M
===
The "rpm -e open-vm-tools" command took 10+ minutes to complete.
===
commandrvf: rpm -e open-vm-tools^M
libguestfs: trace: v2v: command = ""
libguestfs: trace: v2v: aug_load
guestfsd: => command (0x32) took 608.77 secs^M
===
And the selinux relabel took around 5 minutes.
===
commandrvf: setfiles -F -e /sysroot/dev -e /sysroot/proc -e /sysroot/selinux -e /sysroot/sys -m -r /sysroot -v /sysroot/etc/selinux/targeted/contexts/files/file_contexts /sysroot/^M
libguestfs: trace: v2v: rm_f "/.autorelabel"
guestfsd: => selinux_relabel (0x1d3) took 273.91 secs^M
====
I can see the below error randomly getting logged between above jobs.
===
nbdkit: curl[2]: error: pread: curl_easy_perform: HTTP response code said error: The requested URL returned error: 401
nbdkit: curl[2]: debug: pread failed: original errno = 5
nbdkit: curl[2]: debug: retry 1: waiting 2 seconds before retrying
nbdkit: curl[2]: debug: curl: reopen readonly=1 exportname="/"
nbdkit: curl[2]: debug: curl: finalize
nbdkit: curl[2]: debug: curl: close
===
To test, the customer exported the same VM as OVA, copied it to the hypervisor, and then did the convert and the conversion speed was as expected and the issue is only while directly importing from VMware.
The customer also check for possible errors in VMware and was not able to find any.
Version-Release number of selected component (if applicable):
nbdkit-1.22.0-2.module
libguestfs-1.42.0-2.module+el8.3.0+6798+ad6e66be.x86_64
virt-v2v-1.42.0-6.module+el8.3.0+7898+13f907d5.x86_64
How reproducible:
100% for the customer.
Steps to Reproduce:
1. Convert a VMware VM to RHV.
2.
3.
Actual results:
Slow conversion speed while converting VMware VMs to RHV
Expected results:
Additional info:
Comment 2Richard W.M. Jones
2021-02-10 09:36:26 UTC
The biggest single change the customer could make to dramatically improve
performance would be to use VDDK instead of the HTTPS method. Are they
running these conversions by hand?
They are directly importing through RHV web portal which doesn't have the option to use VDDK. I think to use VDDK, they have to either convert by hand or has to use IMS.
The customer tried virt-v2v manually using VDDK transport and was able to achieve good performance (10 minutes vs. 1 hour and 10 minutes).
The request to use VDDK in RHV as rejected in bug 1933656. If there is nothing else to do, we can close this bug.
Comment 9Richard W.M. Jones
2021-11-23 11:03:01 UTC
Closing cantfix since this is an in inherent problem with VMware and
alternatives are available even if RHV doesn't want to use them.