Bug 1469902
| Summary: | Libguestfs should pass copyonread flag through to the libvirt XML | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jaroslav Reznik <jreznik> |
| Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.4 | CC: | dornelas, fgarciad, jherrman, jsuchane, juzhou, kuwei, linl, mtessun, mxie, mzhan, ptoscano, rjones, salmy, tzheng, xiaodwan |
| Target Milestone: | rc | Keywords: | Regression, ZStream |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | V2V | ||
| Fixed In Version: | libguestfs-1.36.3-6.el7_4.1 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, when the libvirt back end to libguestfs was used, the "copyonread" flag was not passed through, which caused performance problems for libguestfs utilities. Notably, the virt-v2v utility was slowed significantly when converting guests from the VMware hypervisor. With this update, "copyonread" is correctly respected when running libguestfs utilities using the libvirt back end. As a result, the described problem no longer occurs.
|
Story Points: | --- |
| Clone Of: | 1466563 | Environment: | |
| Last Closed: | 2017-08-01 11:30:03 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1466563 | ||
| Bug Blocks: | |||
|
Description
Jaroslav Reznik
2017-07-12 04:22:45 UTC
Thanks rjones and Pino for your details explain.And with ‘virt-v2v -v -x’ we can see libvirt XML which has: <driver name="qemu" .... copy_on_read="on" /> So,from comment 4/5/6 , move the bug to VERIFIED. To verify it again, compare the same test convert a guest from vmware to kvm with a linux and a windows (i.e. same input hypervisor, same guest, and same output) with both libguestfs-1.36.3-6.el7.x86_64 and libguestfs-1.36.3-6.el7_4.2.x86_64, and to make a conclude. Scenario 1: with below builds: qemu-kvm-rhev-2.9.0-14.el7.x86_64 kernel-3.10.0-681.el7.x86_64 libvirt-3.2.0-14.el7.x86_64 virt-v2v-1.36.3-6.el7.x86_64 libvirt-2.0.0-10.el7.x86_64 Time: 1:rhel7.3 2210.3s 2:windows10 1798.0 Scenario 2: qemu-kvm-rhev-2.9.0-16.el7_4.2.x86_64 libvirt-3.2.0-14.el7_4.2.x86_64 libguestfs-1.36.3-6.el7_4.2.x86_64 virt-v2v-1.36.3-6.el7_4.2.x86_64 time: 1:rhel7.3 1314.7s 2:windows10 1080.7s So, now the version virt-v2v-1.36.3-6.el7_4.2.x86_64 has a better rate than the version virt-v2v-1.36.3-6.el7.x86_64. 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/RHBA-2017:2332 |