Bug 1165580
Summary: | blkiotune value should be consistent with value in cgroup | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Pei Zhang <pzhang> |
Component: | libvirt | Assignee: | Martin Kletzander <mkletzan> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | dyuan, mkletzan, mzhan, rbalakri, xuzhang |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | libvirt-1.2.17-7.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-19 05:56:25 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
Pei Zhang
2014-11-19 09:28:47 UTC
Patch proposed upstream: https://www.redhat.com/archives/libvir-list/2015-August/msg00065.html Verified version: libvirt-1.2.17-8.el7.x86_64 qemu-kvm-rhev-2.3.0-22.el7.x86_64 verified steps: 1.define and start a guest, check blkiotune value. # virsh blkiotune r72 weight : 1000 device_weight : device_read_iops_sec: device_write_iops_sec: device_read_bytes_sec: device_write_bytes_sec: 1.1. set a iops value that kernel accepts, but does not set them. set the value # virsh blkiotune r72 --device-read-iops-sec /dev/sdb,4294967295 get the value via blkiotune # virsh blkiotune r72 weight : 1000 device_weight : device_read_iops_sec: device_write_iops_sec: device_read_bytes_sec: device_write_bytes_sec: check in cgroup, Nothing ouput # cat /sys/fs/cgroup/blkio/machine.slice/machine-qemu\\x2dr72.scope/blkio.throttle.read_iops_device check domian xml, Nothing output. # virsh dumpxml r72 | grep blkiotune -A 3 1.2 set a normal value that kernel accpets and will set them in cgroup. # virsh blkiotune r72 --device-read-iops-sec /dev/sdb,4294967294 check in cgroup # cat /sys/fs/cgroup/blkio/machine.slice/machine-qemu\\x2dr72.scope/blkio.throttle.read_iops_device 8:16 4294967294 check via blkiotune # virsh blkiotune r72 weight : 1000 device_weight : device_read_iops_sec: /dev/sdb,4294967294 device_write_iops_sec: device_read_bytes_sec: device_write_bytes_sec: check in domian xml : # virsh dumpxml r72 | grep blkiotune -A 3 <blkiotune> <device> <path>/dev/sdb</path> <read_iops_sec>4294967294</read_iops_sec> -- </blkiotune> 2. set a bps value that kernel accepts, but does not set them. # virsh blkiotune r72 --device-write-bytes-sec /dev/sdb,18446744073709551615 get the value via blkiotune # virsh blkiotune r72 weight : 1000 device_weight : device_read_iops_sec: device_write_iops_sec: device_read_bytes_sec: device_write_bytes_sec: check in cgroup, Nothing ouput # cat /sys/fs/cgroup/blkio/machine.slice/machine-qemu\\x2dr72.scope/blkio.throttle.write_bps_device check domian xml, Nothing output. # virsh dumpxml r72 | grep blkiotune -A 3 2.1 set a normal value that kernel accpets and will set them in cgroup. # virsh blkiotune r72 --device-write-bytes-sec /dev/sdb,18446744073709551614 check in cgroup # cat /sys/fs/cgroup/blkio/machine.slice/machine-qemu\\x2dr72.scope/blkio.throttle.write_bps_device 8:16 18446744073709551614 check via blkiotune # virsh blkiotune r72 weight : 1000 device_weight : device_read_iops_sec: device_write_iops_sec: device_read_bytes_sec: device_write_bytes_sec: /dev/sdb,18446744073709551614 check in domain xml # virsh dumpxml r72 | grep blkiotune -A 5 <blkiotune> <device> <path>/dev/sdb</path> <write_bytes_sec>18446744073709551614</write_bytes_sec> </device> </blkiotune> Also tested with lxc using same steps as above. Now the values set via blkiotune are in sync with cgroup. Move to 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. https://rhn.redhat.com/errata/RHBA-2015-2202.html |