Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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
(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.