Bug 1084448 - [BUG] network qos via vnic profile does not work when not using plain ipv4
Summary: [BUG] network qos via vnic profile does not work when not using plain ipv4
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: 3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.5.0
Assignee: Antoni Segura Puimedon
QA Contact: Martin Pavlik
URL:
Whiteboard: network
Depends On: 1084444 1084477 1096806
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-04 11:13 UTC by Sven Kieske
Modified: 2016-02-10 19:38 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-05-27 22:57:30 UTC
oVirt Team: Network
Embargoed:

Attachments (Terms of Use)

Description Sven Kieske 2014-04-04 11:13:16 UTC 
Description of problem:
ovirt network qos relies on libvirt qos elements inside
the domain.xml
however, libvirt fails badly at enforing per device qos rules
instead it filters per protocol and just filters ipv4 traffic.

this leads to no network qos available for other protocols like
ipv6.

Version-Release number of selected component (if applicable):
tested in engine 3.3.3 el6
should reproduce in latest master, even on fedora

How reproducible:
alwayss

Steps to Reproduce:
1. create vnic profile with qos, attach to vm_nic
2. start vm with ipv4 and ipv6 and test vs ipv6 host
3.

Actual results:
qos outbound doesn't work because ipv6 traffic is ignored

Expected results:
it should 'just work' (TM)

Additional info:
See upstream Bug: BZ 1084444
Comment 1 Antoni Segura Puimedon 2014-04-04 11:37:48 UTC 
The problem is on the libvirt side, due to tc filters matching 'protocol ip'. I'll send libvirt a patch.
Comment 2 Sandro Bonazzola 2014-05-08 13:56:42 UTC 
This is an automated message.

oVirt 3.4.1 has been released.
This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed.
Comment 3 Dan Kenigsberg 2014-05-27 22:57:30 UTC 
libvirt-0.10.2-29.el6_5.8 which fixes this bug is now out.
Note You need to log in before you can comment on or make changes to this bug.