Hello James, [big snip]
On 2014-12-28, James Bottomley <jbottom...@parallels.com> wrote: > > The goal is to reduce the size of the patch that has to be applied, but > even if the patch diff reaches zero, we'd still have to build the > supported kernel for you because supporting what someone else builds > becomes a massive fishing expedition into how it was built and > configured. Also note that container development doesn't stop just > because everything that was in OpenVZ has gone upstream, so the vzkernel > will probably be the first one to contain the new features on upstream > track and that alone, given that Parallels is the major developer of new > container features, will probably keep the patch diff non-zero. > > However, as of kernel 3.14, enough of OpenVZ is upstream to bring up > OpenVZ containers on the vanilla kernel. I think this is a wonderful summary of the situation, and I expect will be good enough for many current OpenVZ users (it should be for my purposes). Thanks so much for providing it for us! --keith -- kkel...@wombat.san-francisco.ca.us _______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
