This BZ is to track the deployment side (add a parameter to enable workarounds/enable_numa_live_migration per role and enable it on NFV roles, like dpdk/sriov) +++ This bug was initially created as a clone of Bug #1660852 +++ This is the backport to OSP14. +++ This bug was initially created as a clone of Bug #1660851 +++ Description of problem: As noted in bug 1222414, nova does not currently support live migration of instances with NUMA topologies. The CPU and memory mapping information is not recalculated for the destination host, meaning the instance can fail to boot on a destination host with less cores/hugepages than the source or, worse, actually boot but consume resources dedicated to an existing instance. The long term fix for this is to properly enable live migration for these instances. However, we're seeing issues with this in older versions (and every future version until that feature lands) and the fix won't be backportable to these. In addition, the previous downstream-only workaround for this, seen in bug 1585068 and related bugs, has proven problematic and is not something we want to continue to invest in. As such, we need an upstream-first approach to resolving this issue that can be backported to older versions. The easiest way to do this is to disable live migration of NUMA-based instances by default, providing a workaround flag for users who insist on being able to live migrate even with the issues seen. That is what we've done, and this bug tracks the progress in supporting that downstream. Version-Release number of selected component (if applicable): All supported versions of OSP. How reproducible: See bug 1222414. Steps to Reproduce: See bug 1222414. Actual results: See bug 1222414. Expected results: See bug 1222414. Additional info: --- Additional comment from Red Hat Bugzilla Rules Engine on 2018-12-19 12:17:50 UTC --- This bugzilla has been removed from the release since it is missing the Triaged keyword or does not have an acked release flag. For details, see https://mojo.redhat.com/docs/DOC-1144661#jive_content_id_OSP_Release_Planning.
to clarify, default is false and we only set it to true on dpdk roles
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0878