Comment 7 for bug 1439247

There is some useful discussion under bug 1792985 which has been marked as a dupe of this bug.

Currently it's still not safe to schedule numa-topology and non-numa-topoology on the same compute node because instances with no numa topology can "float" over the whole compute node, which means we have no way of knowing where the memory comes from and therefore can't possibly accurately track memory consumption per NUMA node.

I think it's a cop-out to say "don't schedule numa-topology and non-numa-topology instances on the same compute node". I mean, the way the code is written currently its not safe, but I think we *should* try to make it safe.

Specifically for edge scenarios, we may only have a small number of compute nodes (sometimes just one or two) and so any host-aggregate-based solution doesn't really work. We need to be able to have these things co-exist on a single compute node.

Specifically for 4K memory, this means either disabling "strict" NUMA affinity, or else restricting floating instances to a single NUMA node.