Bug 1146755
| Summary: | [TestOnly] FOO_max for I/O throttling official support on rhel 7.1(qemu-kvm-rhev) | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jun Li <juli> | |
| Component: | qemu-kvm-rhev | Assignee: | Hai Huang <hhuang> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Virtualization Bugs <virt-bugs> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 7.1 | CC: | areis, hhuang, huding, juzhang, virt-maint, xfu | |
| Target Milestone: | rc | Keywords: | TestOnly | |
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1157997 1247830 (view as bug list) | Environment: | ||
| Last Closed: | 2017-06-13 03:55:30 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: | 1150403, 1247688 | |||
| Bug Blocks: | 1157997, 1247830 | |||
|
Description
Jun Li
2014-09-26 02:26:42 UTC
Hi Hai, QE has test this option "FOO_max" in our daily testing, but still exist some issue. Ref following bz: Bug 1150403 - iops_max and iops can not work as expected https://bugzilla.redhat.com/show_bug.cgi?id=1150403 above bz still on "NEW" status and set "Flags: rhel-7.1.0? → rhel-7.2.0?", so I think we can not set this bz to "ON_QA" status. Any mistakes, free to correct me. Thank you. Best Regards, Jun Li Clone this bz to qemu-kvm component[1]. Remove testonly keyword since seems qemu-kvm-rhev supports foo_max with qemu rebase. qemu-kvm does not rebase from qemu1.5. Bug 1247830 - FOO_max for I/O throttling official support on rhel 7.1(qemu-kvm) Best Regards, Junyi on qemu-kvm-rhev-2.3.0-15.el7.x86_64,
boot vm with bps_max, iops_max, bps_rd_max, bps_wr_max, etc
-drive id=drive_image1,if=none,cache=none,snapshot=off,aio=native,format=qcow2,file=/home/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/images/RHEL-Server-6.7-64-virtio-scsi.qcow2 \
-device scsi-hd,id=image1,drive=drive_image1 \
-device scsi-hd,id=image2,drive=drive_image2 \
-device scsi-hd,id=image3,drive=drive_image3 \
-drive id=drive_image2,if=none,cache=none,snapshot=off,aio=native,format=raw,file="/dev/sdb",iops=100,iops_max=1000,bps=4096,bps_max=40960 \
-drive id=drive_image3,if=none,cache=none,snapshot=off,aio=native,format=qcow2,file="/home/RHEL-Server-7.2-64-virtio.qcow2",bps_rd=100,bps_wr=100,bps_rd_max=1000,bps_wr_max=1000,iops_rd=200,iops_wr=200,iops_rd_max=2000,iops_wr_max=2000 \
and limits as expected value in qemu cli
QEMU 2.3.0 monitor - type 'help' for more information
(qemu) info block
drive_image1: /home/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/images/RHEL-Server-6.7-64-virtio-scsi.qcow2 (qcow2)
Cache mode: writeback, direct
drive_image2: /dev/sdb (raw)
Cache mode: writeback, direct
I/O throttling: bps=4096 bps_rd=0 bps_wr=0 bps_max=40960 bps_rd_max=0 bps_wr_max=0 iops=100 iops_rd=0 iops_wr=0 iops_max=1000 iops_rd_max=0 iops_wr_max=0 iops_size=0
drive_image3: /home/RHEL-Server-7.2-64-virtio.qcow2 (qcow2)
Cache mode: writeback, direct
I/O throttling: bps=0 bps_rd=100 bps_wr=100 bps_max=0 bps_rd_max=1000 bps_wr_max=1000 iops=0 iops_rd=200 iops_wr=200 iops_max=0 iops_rd_max=2000 iops_wr_max=2000 iops_size=0
--------------- reset limits to 0, thus remove limits, work as expected.
(qemu) block_set_io_throttle drive_image3 0 0 0 0 0 0
(qemu) info block
drive_image1: /home/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/images/RHEL-Server-6.7-64-virtio-scsi.qcow2 (qcow2)
Cache mode: writeback, direct
drive_image2: /dev/sdb (raw)
Cache mode: writeback, direct
I/O throttling: bps=4096 bps_rd=0 bps_wr=0 bps_max=40960 bps_rd_max=0 bps_wr_max=0 iops=100 iops_rd=0 iops_wr=0 iops_max=1000 iops_rd_max=0 iops_wr_max=0 iops_size=0
drive_image3: /home/RHEL-Server-7.2-64-virtio.qcow2 (qcow2)
Cache mode: writeback, direct
---------------- set *_max in qmp, work as expected.
{ "execute": "block_set_io_throttle", "arguments": { "device": "drive_image3","bps": 204800,"bps_rd": 0,"bps_wr": 0,"iops": 200,"iops_rd": 0,"iops_wr": 0, "bps_max": 2048000}}
{"return": {}}
(qemu) info block
drive_image1: /home/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/images/RHEL-Server-6.7-64-virtio-scsi.qcow2 (qcow2)
Cache mode: writeback, direct
drive_image2: /dev/sdb (raw)
Cache mode: writeback, direct
I/O throttling: bps=4096 bps_rd=0 bps_wr=0 bps_max=40960 bps_rd_max=0 bps_wr_max=0 iops=100 iops_rd=0 iops_wr=0 iops_max=1000 iops_rd_max=0 iops_wr_max=0 iops_size=0
drive_image3: /home/RHEL-Server-7.2-64-virtio.qcow2 (qcow2)
Cache mode: writeback, direct
I/O throttling: bps=204800 bps_rd=0 bps_wr=0 bps_max=2048000 bps_rd_max=0 bps_wr_max=0 iops=200 iops_rd=0 iops_wr=0 iops_max=20 iops_rd_max=0 iops_wr_max=0 iops_size=0
though there *_max related bugs exist, Bug 1202788 - There is no error prompt when set the io throttling parameters FOO_max without FOO and iops_size without iops but the launching of a qemu vm with *_max set is now working. so moving to VERIFIED. |