Bug#710100: lxc-checkconfig inapropriately reports missing CONFIG_CGROUP_NS symbol
Package: lxc Version: 0.8.0~rc1-8+deb7u1 Severity: important * What led up to the situation? This is a clean upgraded Debian, from recent Debian-6 installation * What exactly did you do (or not do) that was effective (or ineffective)? since OpenVZ is missing, I've installed LXC packages, did lxc-create and lxc-start * What was the outcome of this action? lxc-start: No cgroup mounted on the system lxc-start: failed to spawn ... * What outcome did you expect instead? lxc-start: OK. lcx-checkconfig reports some missing components: --- Namespaces --- Namespaces: enabled Utsname namespace: enabled Ipc namespace: enabled Pid namespace: enabled User namespace: enabled Network namespace: enabled Multiple /dev/pts instances: enabled --- Control groups --- Cgroup: enabled Cgroup namespace: CONFIG_CGROUP_NSmissing ^^^ Cgroup device: enabled Cgroup sched: enabled Cgroup cpu account: enabled Cgroup memory controller: enabled Cgroup cpuset: enabled --- Misc --- Veth pair device: enabled Macvlan: enabled Vlan: enabled File capabilities: enabled kernel people say, they don't export such symbol (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710004) -- System Information: Debian Release: 7.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lxc depends on: ii debconf [debconf-2.0] 1.5.49 ii libc6 2.13-38 ii libcap21:2.22-1.2 ii multiarch-support 2.13-38 Versions of packages lxc recommends: ii debootstrap 1.0.48 ii libcap2-bin 1:2.22-1.2 Versions of packages lxc suggests: ii lxctl 0.3.1+debian-2 -- debconf information: lxc/shutdown: /usr/bin/lxc-halt * lxc/directory: /srv/lxc lxc/title: lxc/auto: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710100: lxc-checkconfig inapropriately reports missing CONFIG_CGROUP_NS symbol
severity 710100 minor close 710100 thanks On 05/28/2013 11:12 AM, Rafal Pietrak wrote: kernel people say, they don't export such symbol but they do in 3.8, arch/tile. it's just not applicable for you on your architecture, closing. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710100: lxc-checkconfig inapropriately reports missing CONFIG_CGROUP_NS symbol
On 05/28/2013 11:33 AM, Rafał Pietrak wrote: Can you pls comment on who exactly do you thing should do *something* in their packages, to get LXC correctly start a container with (my) architecture, eg: AMD64 kernel? please read /usr/share/doc/lxc/README.Debian -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710100: lxc-checkconfig inapropriately reports missing CONFIG_CGROUP_NS symbol
Can you pls comment on who exactly do you thing should do *something* in their packages, to get LXC correctly start a container with (my) architecture, eg: AMD64 kernel? the title I've put in this bug report is only my guess of what is wrong. I actually do report: lxc-start: No cgroup mounted on the system; Since this is a fairly fresh install (e.g.: fresh debian6, then immediately upgrade to debian7), if such things do not start out from the box, I consider it a bug. Can you pls help me figureing out who should change what, to have it corrected? thenx, -R On 05/28/2013 11:24 AM, Daniel Baumann wrote: severity 710100 minor close 710100 thanks On 05/28/2013 11:12 AM, Rafal Pietrak wrote: kernel people say, they don't export such symbol but they do in 3.8, arch/tile. it's just not applicable for you on your architecture, closing.
