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

Bug 1157736

Summary: When guest is pinned to NUMA node, emulator threads are still floating
Product: Red Hat OpenStack Reporter: Daniel Berrangé <berrange>
Component: openstack-novaAssignee: Daniel Berrangé <berrange>
Status: CLOSED DUPLICATE QA Contact: Ami Jeain <ajeain>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.0 (RHEL 7)CC: atheurer, berrange, dasmith, mfuruta, ndipanov, pbrady, sbauza, sferdjao, sgordon, tvvcox, vromanso, yeylon
Target Milestone: ---Keywords: ZStream
Target Release: 6.0 (Juno)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-10 15:01:40 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:    
Bug Blocks: 743661, 1038706    

Description Daniel Berrangé 2014-10-27 15:20:50 UTC
Description of problem:
When pinning a guest to a NUMA node, only the vCPU threads are being pinned. The emulator threads are still floating arbitrarily. THis is due to missing

    <emulatorpin cpuset='0-5'/>

data in the <cputune> element.

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


How reproducible:
Always

Steps to Reproduce:
1. Enable the NUMA schedular filter
2. Set  'hw:numa_nodes=2' on a flavor
3. Boot an instance with the flavour
4. Look at the libvirt XML

Actual results:
Missing <emulatorpin> element under <cputune>

Comment 4 Stephen Gordon 2015-02-10 15:01:40 UTC

*** This bug has been marked as a duplicate of bug 1190719 ***