Bug 1734353
Summary: | [cgroup_v2] Error happened and xml not changed when use blkiotune to set blk cgroup values | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux Advanced Virtualization | Reporter: | yisun | |
Component: | libvirt | Assignee: | Pavel Hrdina <phrdina> | |
Status: | CLOSED ERRATA | QA Contact: | yisun | |
Severity: | medium | Docs Contact: | ||
Priority: | unspecified | |||
Version: | --- | CC: | jdenemar, yisun | |
Target Milestone: | rc | |||
Target Release: | 8.0 | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | libvirt-5.6.0-3.el8 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1741825 (view as bug list) | Environment: | ||
Last Closed: | 2019-11-06 07:18:12 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1513930, 1741825 |
Description
yisun
2019-07-30 10:33:34 UTC
When set 2 or more devices concurrently, the error will block the 2nd and rest settings, as follow: $ lsblk | egrep "sda |sdb " sda 8:0 0 465.8G 0 disk sdb 8:16 0 1000M 0 disk $ pwd /sys/fs/cgroup/machine.slice/machine-qemu\x2d9\x2davocado\x2dvt\x2dvm1.scope $ virsh blkiotune avocado-vt-vm1 --device-read-iops-sec /dev/sda,321321,/dev/sdb,123123 error: Unable to change blkio parameters error: internal error: Unable to parse 'rbps=max wbps=max riops=321321 wiops=max' as an integer $ cat io.max 8:0 rbps=max wbps=max riops=321321 wiops=max <===== here, only the /dev/sda setting takes effect. PASSED in auto test job with libvirt-5.6.0-5.module+el8.1.0+4229+2e4e348c.x86_64: https://libvirt-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/libvirt-RHEL-8.1-runtest-x86_64-function-guest_resource_control/10/testReport/ (the single failed case is a script issue, not related to this bz) 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-2019:3723 |