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.
+++ This bug was initially created as a clone of Bug #1084444 +++
Description of problem:
when you specify qos settings according to:
http://libvirt.org/formatnetwork.html#elementQoS
this only gets applied for ipv4 traffic and not e.g. for ipv6
traffic or any other non-ip protocol
Version-Release number of selected component (if applicable):
I guess latest master should still not correctly implement this feature
How reproducible:
always
Steps to Reproduce:
1.define network qos as described above
2. test inside the vm, e.g. ftp with ip dual stack (v4 and v6)
3. watch qos being ignored for v6 traffic
Actual results:
qos gets just applied to deprecated ipv4 protcol
Expected results:
qos gets applied to the whole device, regardless which protocol is used
Additional info:
also backported feature in el6 is affected, also qos in downstream products like
ovirt is affected, as it relies on the libvirt functionality.
reproduced with libvirt-0.10.2-29.el6_5.3.x86_64
Fixed upstream by v1.2.3-50-gd9de144:
commit d9de144385201d66929bf10e1941e30ba43fd746
Author: Antoni S. Puimedon <asegurap>
Date: Fri Apr 4 15:39:33 2014 +0200
QoS: make tc filters match all traffic
Up until now the traffic control filters for the vNIC QoS were
matching only ip traffic. For egress traffic that was unnoticed
because the unmatched traffic would just go to the default htb class
and be shaped anyway. For ingress, though, since the policing of the
rate is done by the filter itself.
The problem is solved by changing protocol to all and making anything
match the filter.
Bug-Url: https://bugzilla.redhat.com/1084444
Signed-off-by: Antoni S. Puimedon <asegurap>
Signed-off-by: Michal Privoznik <mprivozn>
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2014-1374.html