Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1213438

Summary: [vdsm] errors: value of 'vcpu_period' is out of range [1000, 1000000]
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: vdsmAssignee: Martin Sivák <msivak>
Status: CLOSED ERRATA QA Contact: Shira Maximov <mshira>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.5.0CC: bazulay, dfediuck, ecohen, istein, jentrena, lpeer, lsurette, michal.skrivanek, mtessun, pkliczew, sauchter, sbonazzo, sherold, yeylon
Target Milestone: ---Keywords: Performance, ZStream
Target Release: 3.5.3   
Hardware: x86_64   
OS: Linux   
Whiteboard: sla
Fixed In Version: vdsm-4.16.16-1.el6ev Doc Type: Bug Fix
Doc Text:
Cause: The code for computing the cgroup collecting period was wrong and did not anticipate more than 100 CPUs. Consequence: libvirt has a lower bound on the time period and the logic computed this number as constant divided by the number of CPUs. When the number of CPUs was higher than 100, the computed number got smaller than the minimum allowed. Fix: The logic was changed so the time period is kept more constant and the quota value is used more to specify the QoS limits. This also properly reflects the limitation logic when multiple CPUs are present (100% means all CPUs are fully used). Result: No errors and multiple CPU machine obeys the CPU limitations properly.
 Story Points: ---
Clone Of: 1207610 Environment:
Last Closed: 2015-06-15 13:19:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1207610    
Bug Blocks:    

Comment 3 errata-xmlrpc 2015-06-15 13:19:08 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.

https://rhn.redhat.com/errata/RHBA-2015-1103.html
Comment 4 Ilanit Stein 2015-09-03 20:38:26 UTC 
QE: Test case should be added for this bug, with a flow based on bug 1207610, comment 25.