[Openstack-operators] Migrating an instance to a host with less cores fails

Steve Gordon sgordon at redhat.com
Fri Sep 25 21:18:51 UTC 2015


----- Original Message -----
> From: "Chris Friesen" <chris.friesen at windriver.com>
> To: openstack-operators at lists.openstack.org
> 
> On 09/25/2015 12:34 PM, Steve Gordon wrote:
> 
> > Nikola's reply got bounced because he isn't subscribed, but:
> >
> > """
> > Thanks Steve!
> >
> > So the below is likely the same root cause as this bug:
> >
> > https://launchpad.net/bugs/1461777
> >
> > Which has been fixed in Liberty and backported to stable/kilo (see
> > https://review.openstack.org/#/c/191594/)
> >
> > Updating your lab to the latest stable/kilo release (2015.1.1) will
> > likely fix the problem for you.
> >
> > Let me know if this helps!
> 
> My concern with that patch is that it only applies if there is no numa
> topology
> for the instance.  I think it's possible to specify hugepages but not CPU
> pinning, in which case there would still be a numa topology for the instance,
> it
> just wouldn't have pinned CPUs in it.
> 
> Chris

I think everyone involved shares that concern but the NUMA-related features (incl. huge pages) were at least as I understand it supposed to be opt in, the above patch at least alleviates the issues caused for those who never opted into them and got caught up in these unintended side effects.

-Steve



More information about the OpenStack-operators mailing list