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 1084477 - [BUG] Quality of service does just apply to protocol "ip" instead of the device
Summary: [BUG] Quality of service does just apply to protocol "ip" instead of the device
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Michal Privoznik
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1084444
Blocks: 1084448 1096806
TreeView+ depends on / blocked
 
Reported: 2014-04-04 12:46 UTC by Dan Kenigsberg
Modified: 2014-10-14 04:21 UTC (History)
11 users (show)

Fixed In Version: libvirt-0.10.2-33.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 1084444
Environment:
Last Closed: 2014-10-14 04:21:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1374 0 normal SHIPPED_LIVE libvirt bug fix and enhancement update 2014-10-14 08:11:54 UTC

Description Dan Kenigsberg 2014-04-04 12:46:31 UTC
+++ 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

Comment 3 Jiri Denemark 2014-04-09 09:55:28 UTC
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>

Comment 4 hongming 2014-04-10 05:32:02 UTC
Can reproduce it in libvirt-0.10.2-29.el6_5.4.x86_64

# virsh net-dumpxml default
<network>
  <name>default</name>
  <uuid>ffc4e572-1c97-43b7-a54b-f3995e9fd3ef</uuid>
  <forward mode='nat'/>
  <bridge name='virbr0' stp='on' delay='0' />
  <mac address='52:54:00:85:27:9F'/>
  <bandwidth>
    <inbound average='512' peak='1024' burst='32'/>
    <outbound average='512' peak='1024' burst='32'/>
  </bandwidth>
  <ip address='192.168.122.1' netmask='255.255.255.0'>
    <dhcp>
      <range start='192.168.122.2' end='192.168.122.254' />
    </dhcp>
  </ip>
</network>

# tc -d filter show dev virbr0 parent ffff:
filter protocol ip pref 49152 u32 
filter protocol ip pref 49152 u32 fh 800: ht divisor 1 
filter protocol ip pref 49152 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid :1 
  match 00000000/00000000 at 12
 police 0x1 rate 4096Kbit burst 32Kb mtu 64Kb action drop overhead 0b 
ref 1 bind 1

Comment 7 hongming 2014-04-17 06:15:32 UTC
Verify it using libvirt-0.10.2-33.el6.x86_64. The result is expected. Move its status to VERIFIED.


# virsh net-dumpxml default
<network>
  <name>default</name>
  <uuid>ebfbd87d-cf22-483a-bfb7-776add027844</uuid>
  <forward mode='nat'/>
  <bridge name='virbr0' stp='on' delay='0' />
  <mac address='52:54:00:30:BC:DF'/>
  <bandwidth>
    <inbound average='512' peak='1024' burst='32'/>
    <outbound average='512' peak='1024' burst='32'/>
  </bandwidth>
  <ip address='192.168.122.1' netmask='255.255.255.0'>
    <dhcp>
      <range start='192.168.122.2' end='192.168.122.254' />
    </dhcp>
  </ip>
</network>

# tc -d filter show dev virbr0 parent ffff:
filter protocol all pref 49152 u32 
filter protocol all pref 49152 u32 fh 800: ht divisor 1 
filter protocol all pref 49152 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid :1 
  match 00000000/00000000 at 0
 police 0x1 rate 4096Kbit burst 32Kb mtu 64Kb action drop overhead 0b 
ref 1 bind 1

Comment 10 errata-xmlrpc 2014-10-14 04:21:05 UTC
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


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