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 515694 - RFE: Support disk I/O bandwidth limitation / priority control
Summary: RFE: Support disk I/O bandwidth limitation / priority control
Keywords:
Status: CLOSED DUPLICATE of bug 632492
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Jiri Denemark
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 598438 (view as bug list)
Depends On:
Blocks: 519868 554544 575275 Rhel6.1LibvirtTier2
TreeView+ depends on / blocked
 
Reported: 2009-08-05 12:25 UTC by Daniel Berrangé
Modified: 2011-03-09 09:20 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-23 21:06:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Daniel Berrangé 2009-08-05 12:25:24 UTC
Description of problem:
There needs to be a mechanism to enforce disk I/O bandwidth for guest virtual machines. For the QEMU driver, this could be done using the CLONE_IO flag & io priority schedular tunable. CGroups may also soon gain a block IO controller that could be used.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 RHEL Program Management 2009-08-05 12:49:56 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 Daniel Veillard 2009-10-08 12:34:50 UTC
No work has been done upstream about this, and this requires a new API and
much testing, this is IMHO really at risk at this point so Cond NACK on 
Upstream,

Daniel

Comment 5 Vivek Goyal 2010-02-16 15:20:51 UTC
The basic weight based proportional BW division IO controller (blkio) patches went upstream (available in current 2.6.33-rc8) and are also available in RHEL6 kernel. It would be good if we can have some kind of support for it in libvirt.

A quick HOWTO is available in kernel sources. Documentation/cgroups/blkio-controller.txt.

Alternatively, one can find it here.

http://www.linuxhq.com/kernel/v2.6/32-git15/Documentation/cgroups/blkio-controller.txt

Comment 6 Daniel Berrangé 2010-06-01 12:12:58 UTC
*** Bug 598438 has been marked as a duplicate of this bug. ***

Comment 8 Dave Allan 2010-11-23 21:06:28 UTC

*** This bug has been marked as a duplicate of bug 632492 ***


Note You need to log in before you can comment on or make changes to this bug.