search for: cgclassify

...\\x2dpuppet.infra.scope/memory.memsw.limit_in_bytes 18203869184 In our case limit exists and set to 16Gb mem and 16+1 Gb for mem +swap Contaner name puppet.infra, substitute here your container name. 2) if exists - simple attach cgroups to libvirt_lxc pid : node# yum install libcgroup-tools node# cgclassify -g memory:machine.slice/machine-lxc\\x2dLXC_CONTAINER_NAME.scope PID where pid in my case found as: [root@node]# ps ax | grep libvirt_lxc | grep -v grep | grep puppet 22254 ? Sl 296:25 /usr/libexec/libvirt_lxc --name puppet.infra --console 24 --security=none --handshake 42 --veth macvl...

Has anyone seen this issue? We're running containers under CentOS 7.2 and some of these containers are reporting incorrect memory allocation in /proc/meminfo. The output below comes from a system with 32G of memory and 84GB of swap. The values reported are completely wrong. # cat /proc/meminfo MemTotal: 9007199254740991 kB MemFree: 9007199224543267 kB MemAvailable: 12985680

On 03/24/2016 02:26 AM, mxs kolo wrote: > use libvirt 1.3.2, it's more stable and never show negative values > for memory and swap inside container > The latest version available for CentOS/RHEL is version 1.2.17. What site are you using to get the rpm for version 1.3.2? Peter

...s when running our software in containers under > this environment. Unfortunately we're out of time to address these 7.2 > issues, so for now we're rolling everything back to 7.1 and will > postpone 7.2 tests until our next release cycle starts. anyway, I believe that solution with cgclassify would work in case 1.2.17 b.r. Maxim Kozin

Hi all I have CentOS Linux release 7.0.1406, libvirt 1.2.7 installed. Just after create and start inside LXC container present cgroups. Example for memory: [root@ce7-t1 /]# ls -la /sys/fs/cgroup/memory/ total 0 drwxr-xr-x 2 root root 0 Sep 15 17:14 . drwxr-xr-x 12 root root 280 Sep 15 17:14 .. -rw-r--r-- 1 root root 0 Sep 15 17:14 cgroup.clone_children --w--w--w- 1 root root 0 Sep 15