On Wed, Feb 14, 2018 at 01:47:42PM +0300, Konstantin Khorenko wrote:
> Makes sense to release it as a ReadyKernel patch?
I don't see any point in it: this only helps VZ nested in ESXi or
Hyper-V, which is probably used only in evaluation or demo scenarios.
I'm pretty confident we have zero existin
Makes sense to release it as a ReadyKernel patch?
Or the code is executed too early, so modules won't be loaded yet?
--
Best regards,
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
On 02/14/2018 01:43 PM, Konstantin Khorenko wrote:
The commit is pushed to "branch-rh7-3.10.0-693.17.1.vz7.43.
The commit is pushed to "branch-rh7-3.10.0-693.17.1.vz7.43.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-693.17.1.vz7.43.4
-->
commit 988f48689f68fe80186f2ec994e4f135769c1d1b
Author: Vitaly Kuznetsov
Date: Wed Feb 14 13:43:38 2018 +0300
ms/x86/k
