Bug 1333195

Summary: CPU isolated thread policy is not working properly.
Product: Red Hat OpenStack Reporter: Stephen Gordon <sgordon>
Component: openstack-novaAssignee: Eoghan Glynn <eglynn>
Status: CLOSED NOTABUG QA Contact: Prasanth Anbalagan <panbalag>
Severity: high Docs Contact:
Priority: unspecified    
Version: 9.0 (Mitaka)CC: berrange, dasmith, eglynn, kchamart, nlevinki, panbalag, rnoriega, sbauza, sferdjao, sgordon, srevivo, vromanso
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1332907 Environment:
Last Closed: 2016-05-06 11:26:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1332907, 1333196    
Bug Blocks: 1277736    

Description Stephen Gordon 2016-05-04 22:23:11 UTC 
+++ This bug was initially created as a clone of Bug #1332907 +++

Description of problem:

Isolated thread policy is not working properly according to documentation.

Version-Release number of selected component (if applicable):


How reproducible:

Highly

Steps to Reproduce:

 Check https://bugs.launchpad.net/nova-solver-scheduler/+bug/1578150

Actual results:

 Sibling threads are used when the correspondent thread is ocuppied by an isolated vCPU.

Expected results:

 Have one thread per core unused.

Additional info:

 Check https://bugs.launchpad.net/nova-solver-scheduler/+bug/1578150
Comment 1 Stephen Gordon 2016-05-05 17:52:53 UTC 
*** Bug 1333196 has been marked as a duplicate of this bug. ***
Comment 2 Daniel Berrangé 2016-05-06 11:26:53 UTC 
Commented on the upstream bug - the reporter was trying to run guests with overcommit floating CPUs on the same host as guests with dedicated pinned CPUs. They should have been using host aggregates to separate these guests onto different hosts.