Public bug reported:
When pinning a guest to a specific NUMA node, the Nova libvirt driver
does not pin the emulator threads to any host CPUs. This means that non-
vCPU related work done by QEMU is still free to float across any host
NUMA node.
The expected behaviour is that the emulator threads are pinned to the
union of host CPUs that all vCPUs are pinned to.
** Affects: nova
Importance: Medium
Assignee: Daniel Berrange (berrange)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => Daniel Berrange (berrange)
** Changed in: nova
Importance: Undecided => Medium
** Changed in: nova
Status: New => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1386162
Title:
Nova libvirt driver does not bind emulator threads to host CPUs
Status in OpenStack Compute (Nova):
In Progress
Bug description:
When pinning a guest to a specific NUMA node, the Nova libvirt driver
does not pin the emulator threads to any host CPUs. This means that
non-vCPU related work done by QEMU is still free to float across any
host NUMA node.
The expected behaviour is that the emulator threads are pinned to the
union of host CPUs that all vCPUs are pinned to.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1386162/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
