Some workloads require to have hypervisor overheads to be isolated
from the set of pCPUs running guest vCPUs threads.
For libvirt driver we have introduced the emulator threads placements
which provides an option to reserve an additional host CPU per guest
to pin the emulator threads on .
To extend the flexibility and address use-cases where resources on
hosts are limited. We are introducing 'overheadpinset' option on
compute node. Operators will have ability to reserve host CPUs for
For case of libvirt driver we are extending the flavor property
hw:emulatorthreadspolicy to accept 'host' value, meaning that the
guests configured to use hw:emulatorthreadspolicy=host will have
their emulator threads running on the set of pCPUs configured with
The blueprint  on launchpad.net, patches  and spec updated 
OpenStack Development Mailing List (not for usage questions)