Hi, Yuri.

Could you please share more benefits for your business related to implementation of this functionality?

A good ideia is replace the OpenVZ support to LXC.

LXC kernel support is already enabled in almost all current Kernels that have cgroups isolation (including CloudLinux kernels, in fact the cgroup is probably the base of LVE in CL7 and CL8). So theres no need to do big changes in the kernels. The big change will be allow LVEs cgroups and isolations to run as nested container inside a LXC container.

May this also be used as base to allow some nested isolations inside a LVE just like having another containers inside LVE just like docker allowing a cPanel user for example to start isolated containers inside it account with some kind of fake root and virtual networking putting each project in isolated containers to avoid hacking hazard across account and running everything it need inside the LVE resources limit.

https://cloudlinux.uservoice.com/forums/269295-general/suggestions/34622584-lxc-support-since-lxc-replaces-openvz-in-most-pop

I think should invest time to finish it before adding new functions, since it will become more complicated to support OpenVZ with more features.