Bug 1207122
Summary: | Wrong speed show from blockjob while set bandwidth to 1 when do blockcopy | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Shanzhi Yu <shyu> |
Component: | libvirt | Assignee: | Peter Krempa <pkrempa> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | dyuan, lhuang, mzhan, rbalakri |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | libvirt-1.2.14-1.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-19 06:26:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Shanzhi Yu
2015-03-30 09:43:22 UTC
Fixed upstream: commit 3c6a72d5376732efd8effb4a0a419211c0eb0659 Author: Peter Krempa <pkrempa> Date: Mon Mar 30 17:34:13 2015 +0200 qemu: blockCopy: Pass adjusted bandwidth when called via blockRebase The block copy API takes the speed in bytes/s rather than MiB/s that was the prior approach in virDomainBlockRebase. We correctly converted the speed to bytes/s in the old API but we still called the common helper virDomainBlockCopyCommon with the unadjusted variable. v1.2.14-rc1-14-g3c6a72d Verify this bug with libvirt-1.2.16-1.el7.x86_64 1. prepare transient guest # virsh list --transient Id Name State ---------------------------------------------------- 11 r7 running 2. Do block copy with bandwidth equal 1 # virsh blockcopy r7 vda /var/lib/libvirt/images/r7.copy --verbose --wait 1 Block Copy: [ 98 %] 3. Open another terminal, check the blockjob info # virsh blockjob r7 vda Block Copy: [ 1 %] Bandwidth limit: 1048576 bytes/s (1.000 MiB/s) So, verify this bug 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://rhn.redhat.com/errata/RHBA-2015-2202.html |