Bug 1084448

Summary: [BUG] network qos via vnic profile does not work when not using plain ipv4
Product: [Retired] oVirt Reporter: Sven Kieske <s.kieske>
Component: vdsmAssignee: Antoni Segura Puimedon <asegurap>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Pavlik <mpavlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.4CC: acathrow, asegurap, bazulay, bugs, danken, gklein, iheim, mgoldboi, myakove, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-27 22:57:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1084444, 1084477, 1096806    
Bug Blocks:    

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.