The standard kernel config for 16.04 has:
...
CONFIG_MEMCG=y
CONFIG_MEMCG_SWAP=y
# CONFIG_MEMCG_SWAP_ENABLED is not set
...
I've not re-compiled with CONFIG_MEMCG_SWAP_ENABLED set to see if it
fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I had enconntered this same issue. I am not quite sure if it's CONFIG_*
option not enabled or else however I was able to remedy the issue by
adding 'swapaccount=1' to the kernel line. That in turn enabled
memory.memsw.* options in cgroups. Hope this helps you.
Sincerely yours,
LH
--
You receive
First you need to convince me that this is a kernel bug.
How come libvirt's LXC driver is trying to use a /sys API that doesn't
even exist in the very latest mainline kernel?
I would guess that either libvirt assumes the kernel is built with some
option that the Ubuntu kernel hasn't been built wi
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.
Please follow the instructions on th
After updating to that kernel (under 14.04), the problem is not fixed.
$ uname -a
Linux kit1 3.19.0-031900rc4-generic #201501112135 SMP Sun Jan 11 21:36:48 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
* The LXC instance still does not start if the 131072 setting is included.
$ virsh -c lxc: start go
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.19 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
