The downside to such a strategy is that there is a risk that nobody ever
gets around to implementing useful controllers, so it ends up dead code. I'd judge that the interest in resource management is such that the risk of
this happening is low.
I think the risk is that OpenVZ has all the controls and resource
managers we need, while CKRM is still more research-ish. I find the
OpenVZ code much clearer, cleaner and complete at the moment, although
also much more conservative in its approach to solving problems.