Quoting John (j...@neutrondawn.com):
Greetings LXC,
im having problems getting my container operational on centos. cgconfig
and cgred are both running. the error is as follows during startup
attempts:
lxc-start 1381364626.764 DEBUGlxc_cgroup - cgroup_path_get: called
for subsys
I am in fact able to write to the file. its initial state is empty.
On 2013-10-10 09:24, Serge Hallyn wrote:
Quoting John (j...@neutrondawn.com):
Greetings LXC,
im having problems getting my container operational on centos.
cgconfig
and cgred are both running. the error is as follows
Quoting John (j...@neutrondawn.com):
I am in fact able to write to the file. its initial state is empty.
The initial state of which file is empty -
/cgroup/cpuset/lxc/cpuset.cpus, or /cgroup/cpuset/lxc/GE/cpuset.cpus?
If the former, then that's the problem. That file should have been
Serge,
Sorry for the confusion, both files have been created and are in fact
empty. This is after having removed any configuration constraint on
processors in GE.conf.
On 2013-10-10 10:03, Serge Hallyn wrote:
Quoting John (j...@neutrondawn.com):
I am in fact able to write to the file. its
On Thu, 10 Oct 2013 09:03:36 -0500
Serge Hallyn serge.hal...@ubuntu.com wrote:
Quoting John (j...@neutrondawn.com):
I am in fact able to write to the file. its initial state is empty.
The initial state of which file is empty -
/cgroup/cpuset/lxc/cpuset.cpus, or
On 2013-10-10 17:44, Dwight Engen wrote:
On Thu, 10 Oct 2013 09:03:36 -0500
Serge Hallyn serge.hal...@ubuntu.com wrote:
John, are you perhaps running on an older kernel that doesn't have
clone_children? lxc relies on this to propagate values down the
heirarchy.
Dear Serge, Dear Jon
On my
On 2013-10-10 18:34, John wrote:
Guido, Serge
Thank you for your insight. the parent, /cgroup/cpuset/lxc, has cpuset.cpus
however it hasnt been initialized to any number. my hypothesis is
/cgroup/cpuset/lxc/GE/cpuset.cpus therefore cannot be set as its parent hasnt
been initialized.
Guido,
Alas, this appears to be the problem. /cgroups/cgroup.clone_children
does not exist.
Thanks for the assistance, ill likely begin testing with a new kernel.
A workaround for this problem in RHEL/Centos that sidesteps the kernel
recompile issue is to permit containers to have access to
Quoting John (j...@neutrondawn.com):
Guido,
Alas, this appears to be the problem. /cgroups/cgroup.clone_children
does not exist.
Thanks for the assistance, ill likely begin testing with a new kernel.
A workaround for this problem in RHEL/Centos that sidesteps the kernel
recompile
