* Ian jonhson <jonhson.ian@xxxxxxxxx> [2008-12-12 17:06:21]: > > With what version of the kernel due you see this problem. The memory > > controller is undergoing a churn and I think we found something that > > potentially breaks the memory controller in the current -mm. To verify > > > I am not sure whether the -mm is opened. I just opened the options as > said in REAEME of lxc-0.3.0. And, the kernel version in my VM is: > 2.6.27-rc8. > OK, so this is not an lxc kernel, but a mainline kernel. > > > 1. Can you see the memory.usage_in_bytes corresponding to the control > > group where you run the container > > How can I know the number correspond to the control group? >From outside the container, figure out the process id of init and then do a cat /proc/<pid>/cgroup. Then go to that directory and cat memory.usage_in_bytes, memory.stat and memory.limit_in_bytes to verify the setup > > > 2. Check tasks file to see that the container tasks are indeed in the > > container. > > > > My program forks a child and its child (grandson of previous process) call the > the /bin/bash to open a shell. I just can find the parent process is > in container > tasks file, but its child and grandson process are not. > Hmmm.. but the child and grandson are alive right? Do a cat /proc/<pid>/cgroup on them to see where they went or where they are. -- Balbir _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
