yahoo-eng-team team mailing list archive

[Artom Lifshitz <2077228@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

This is more of a libvirt (or maybe even lower down in the kernel) bug,
but the consequence of $topic's reporting is that if libvirt CPU power
management is enabled, we mess up our NUMA accounting because we have
the wrong socket for some/all of our dedicated CPUs, depending on
whether they were online or not when we called get_capabilities().

Initially found by internal Red Hat testing, and reported here:
https://issues.redhat.com/browse/OSPRH-8712

** Affects: nova
     Importance: Undecided
         Status: 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/2077228

Title:
  libvirt reports powerd down CPUs as being on socket 0 regardless of
  their real socket

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  This is more of a libvirt (or maybe even lower down in the kernel)
  bug, but the consequence of $topic's reporting is that if libvirt CPU
  power management is enabled, we mess up our NUMA accounting because we
  have the wrong socket for some/all of our dedicated CPUs, depending on
  whether they were online or not when we called get_capabilities().

  Initially found by internal Red Hat testing, and reported here:
  https://issues.redhat.com/browse/OSPRH-8712

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2077228/+subscriptions