RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1146755 - [TestOnly] FOO_max for I/O throttling official support on rhel 7.1(qemu-kvm-rhev)
Summary: [TestOnly] FOO_max for I/O throttling official support on rhel 7.1(qemu-kvm-r...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Hai Huang
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1150403 1247688
Blocks: 1157997 1247830
TreeView+ depends on / blocked
 
Reported: 2014-09-26 02:26 UTC by Jun Li
Modified: 2017-06-13 03:55 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1157997 1247830 (view as bug list)
Environment:
Last Closed: 2017-06-13 03:55:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jun Li 2014-09-26 02:26:42 UTC 
Description of problem:
File this new bug only to record adding these new options(bps_max/bps_rd_max/bps_wr_max/iops_max/iops_rd_max/iops_wr_max/iops_size) on rhel 7.1(qemu-kvm-rhev). These options will be official supported, too.

QE found these options has been included in qemu-kvm-rhev-2.1.0-4.el7.x86_64.
So, QE will close this bz when these new options functional testing finished. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Jun Li 2015-01-16 09:47:54 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
Comment 11 juzhang 2015-07-29 03:24:20 UTC 
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
Comment 12 Xiaoqing Wei 2015-08-10 09:49:27 UTC 
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
Comment 13 Xiaoqing Wei 2015-08-10 09:52:07 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.