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.

Description of problem:
QEMU has a throttling module that can be used to set limits to I/O operations. But the virtualization solutions that are based on libvirt would need this mechanism to be available in libvirt in order to manage throttle groups.

Additional info:
Parameters like "iops-total", "iops-total-max" and "group" should be made available through libvirt.

Libvirt allows setting throttling parameters on the disk level via following config:

<devices>
  <disk type='file'>
    [...]
    <source file='/var/lib/libvirt/images/blah.img'/>
    [...]
    <iotune>
      <total_bytes_sec>10000000</total_bytes_sec>
      <read_iops_sec>400000</read_iops_sec>
      <write_iops_sec>100000</write_iops_sec>
    </iotune>

See the documentation for the <iotune> sub-element of https://www.libvirt.org/formatdomain.html#devices for other available trottling parameters including those you've requested.

In case you require a more complex configuration please make sure to raise that with your support representative and include a more detailed description of your use case so that we can evaluate it.