Initially features were used in order to prevent CT owners
from some functionality which might be dangerous or
lead to some restrictions on the CT management like
a CT with NFSd inside cannot be migrated online.
In PCS6 we already had VE_FEATURE_IPGRE feature deprecated
and now we don't see any re
The commit is pushed to "branch-rh7-3.10.0-229.7.2.vz7.8.x-ovz" and will appear
at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-229.7.2.vz7.8.5
-->
commit a7e1413049ff1d97e0e726fb1e58fb631e0dbcd6
Author: Trond Myklebust
Date: Fri Oct 9 15:13:58 2015 +0400
ms/SUNRPC: NUL
The commit is pushed to "branch-rh7-3.10.0-229.7.2.vz7.8.x-ovz" and will appear
at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-229.7.2.vz7.8.5
-->
commit 781762e43ead370b86cf23d71d3cf9bf0e893c35
Author: Andrey Ryabinin
Date: Fri Oct 9 15:14:08 2015 +0400
ms/lockd: crea
On 09.10.2015 13:55, Konstantin Khorenko wrote:
> Initially features were used in order to prevent CT owners
> from some functionality which might be dangerous or
> lead to some restrictions on the CT management like
> a CT with NFSd inside cannot be migrated online.
>
> In PCS6 we already had V
On 09/17/2015 12:45 PM, Cyrill Gorcunov wrote:
On Thu, Sep 17, 2015 at 12:24:29PM +0300, Vladimir Davydov wrote:
On Fri, Sep 11, 2015 at 10:06:34PM +0300, Cyrill Gorcunov wrote:
Currently we allow to mount cgroups from inside of VEs context becuse
otherwise we simply can't restore them in other
On Fri, Oct 09, 2015 at 04:23:51PM +0300, Konstantin Khorenko wrote:
> >I believe in this case it won't be needed. At the moment we start
> >criu inside VE exactly because we're to create venet :(
>
> Ok, than not applying this, will try to prohibit mounting cgroups inside a CT
> after we start ma
The commit is pushed to "branch-rh7-3.10.0-229.7.2.vz7.8.x-ovz" and will appear
at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-229.7.2.vz7.8.5
-->
commit ce4090d533cf8b50434a4bfc8dd8861ebe21d665
Author: Konstantin Khorenko
Date: Fri Oct 9 18:03:10 2015 +0400
ve: mark S
This reverts commit 4c6ca842a16f63816407247a696360b77348a566.
The information about the resource usage of tasks when OOM is
triggered often is the only source of info which can be investigated
to understand if there is a problem on the node =>
enable it by default back.
OOM reports are ratelimite
