Bug 1247830

Summary: FOO_max for I/O throttling official support on rhel 7.1(qemu-kvm)
Product: Red Hat Enterprise Linux 7 Reporter: juzhang <juzhang>
Component: qemu-kvmAssignee: Stefan Hajnoczi <stefanha>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.2CC: areis, hhuang, huding, juli, juzhang, knoel, rbalakri, virt-bugs, virt-maint, xfu
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1146755 Environment:
Last Closed: 2015-07-31 06:48:02 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: 1146755, 1150403, 1247688    
Bug Blocks: 1157997    

Comment 1 juzhang 2015-07-29 03:25:08 UTC 
Remove Testonly keyword since seems qemu-kvm-rhev supports foo_max with qemu rebase but qemu-kvm does not rebase from qemu1.5. Should new feature for qemu-kvm build.

Best Regards,
Junyi
Comment 3 Ademar Reis 2015-07-30 14:54:35 UTC 
(In reply to juzhang from comment #1)
> Remove Testonly keyword since seems qemu-kvm-rhev supports foo_max with qemu
> rebase but qemu-kvm does not rebase from qemu1.5. Should new feature for
> qemu-kvm build.

So I understand this BZ is asking for the backport of *_max I/O throttling parameters. That would mean the backport of the new I/O throttling implementation and I don't think it's worth the effort, unless we have a customer request approved by PM.

I'm closing it as WONTFIX for RHEL7. Please reopen if I'm mistaken.