Comment 5 for bug 1792985

Jay, in the document you mention the bit you quote is specifically in a section on CPU pinning. I don't think it will be obvious to operators that the warning is intended to apply to instances with hugepages or PCI devices as well as pinned CPUs. Also, the reason that warning was added was because we didn't account for the CPU resources. I don't think anyone realized there was a memory issue as well.

On the discussion for the "Support shared and dedicated VMs in one host" spec (https://review.openstack.org/#/c/543805/) Sylvain explicitly redirected discussion towards your "Standardize CPU resource tracking" spec, implying that it would enable the ability to have shared and dedicated VMs on one host.

That, combined with the "NUMA Topology with Resource Providers" spec would make it possible to properly track per-node resources, which would make it possible to reliably mix NUMA-pinned instances and non-NUMA-pinned instances.

We've sorted out the handling of floating vs pinned CPUs, the only remaining thing is how to handle 4K memory consumption of instances with floating CPUs. It seems arbitrary to me for us to leave this one gap since as far as I can see it's the last blocker.