Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

cpuset.mems: numerical result out of range #2176

Closed
lauatic opened this issue Nov 8, 2019 · 1 comment · Fixed by #2944
Closed

cpuset.mems: numerical result out of range #2176

lauatic opened this issue Nov 8, 2019 · 1 comment · Fixed by #2944
Assignees
@egernst
Labels
bug Incorrect behaviour

Comments

@lauatic
Copy link

lauatic commented Nov 8, 2019

Description of problem

My environment configured containerd with kata-runtime.  I followed the setup instructions on https://github.com/kata-containers/documentation/blob/master/how-to/containerd-kata.md#configuration and packaging/kata-deploy/scripts/kata-deploy.sh

When I create a kata container in this environment, I got this error message.  Anyone know how I can resolve this?

rpc error: code = Unknown desc = failed to create containerd task: Could not run process: container_linux.go:346: starting container process caused "process_linux.go:297: applying cgroup configuration for process caused "failed to write 0,1 to cpuset.mems: write /sys/fs/cgroup/cpuset/k8s.io/f1fdd8d5be9030388e4e04dd7d42df9e77a3d46ecb4922ecb2936bf92f74595d/cpuset.mems: numerical result out of range"": unknown 

kata-runtime  : 1.8.2
   commit   : cdc30296c370414d8ef445abd06378199775d076
   OCI specs: 1.0.1-dev

containerd github.com/containerd/containerd 1.2.4 e6b3f5632f50dbc4e9cb6288d911bf4f5e95b18e

$ cat /etc/containerd/config.toml. . .        [plugins.cri.containerd.runtimes.kata]
          runtime_type = "io.containerd.kata.v2"
          [plugins.cri.containerd.runtimes.kata.options]
            ConfigPath = "/etc/kata-containers/configuration.toml"
      [plugins.cri.cni]
        bin_dir = "/opt/cni/bin"
        conf_dir = "/etc/cni/net.d"
        conf_template = ""

(replace this text with the list of steps you followed)

Expected result

(replace this text with an explanation of what you thought would happen)

Actual result

(replace this text with details of what actually happened)
@lauatic lauatic added bug Incorrect behaviour needs-review Needs to be assessed by the team. labels Nov 8, 2019
@egernst egernst self-assigned this Sep 10, 2020
@egernst egernst added bug Incorrect behaviour and removed bug Incorrect behaviour needs-review Needs to be assessed by the team. labels Sep 10, 2020
@egernst
Copy link
Member

egernst commented Sep 10, 2020

I have seen this as well. The guest doesn't have a notion of topology at this point, and it doesn't make sense to set cpuset.mems. We should, however, set it on host side.

I'll resolve this failure first, then look at adding cpuset.mems support to the overall pod (we do this for cpuset.cpus on latest today).

egernst added a commit to egernst/runtime that referenced this issue Sep 10, 2020
@egernst
cpuset: don't set cpuset.mems in the guest
d96296f 
Kata doesn't map any numa topologies in the guest. Let's make sure we
clear the Cpuset fields before passing container updates to the
guest. Without this, we could encounter a runtime failure:

```
process_linux.go:297: applying cgroup configuration for process caused
"failed to write 0,1 to cpuset.mems: writea 0,1 to cpuset.mems: write
0,1 to cpuset.mems: write /sys/fs/cgroup/cpuset .... /cpuset.mems:
numerical result out of range"": unknown
```

Note, in the future we may want to have a vCPU to guest CPU mapping and
still include the cpuset.Cpus. Until we have this support, clear this as
well.

Fixes: kata-containers#2176

Signed-off-by: Eric Ernst <[email protected]>
@egernst egernst mentioned this issue Sep 10, 2020
Merged
egernst added a commit to egernst/runtime that referenced this issue Sep 10, 2020
@egernst
cpuset: don't set cpuset.mems in the guest
18098a6 
Kata doesn't map any numa topologies in the guest. Let's make sure we
clear the Cpuset fields before passing container updates to the
guest. Without this, we could encounter a runtime failure:

```
process_linux.go:297: applying cgroup configuration for process caused
"failed to write 0,1 to cpuset.mems: writea 0,1 to cpuset.mems: write
0,1 to cpuset.mems: write /sys/fs/cgroup/cpuset .... /cpuset.mems:
numerical result out of range"": unknown
```

Note, in the future we may want to have a vCPU to guest CPU mapping and
still include the cpuset.Cpus. Until we have this support, clear this as
well.

Fixes: kata-containers#2176

Signed-off-by: Eric Ernst <[email protected]>
egernst added a commit to egernst/runtime that referenced this issue Sep 10, 2020
@egernst
cpuset: don't set cpuset.mems in the guest
b5b8870 
Kata doesn't map any numa topologies in the guest. Let's make sure we
clear the Cpuset fields before passing container updates to the
guest. Without this, we could encounter a runtime failure:

```
process_linux.go:297: applying cgroup configuration for process caused
"failed to write 0,1 to cpuset.mems: writea 0,1 to cpuset.mems: write
0,1 to cpuset.mems: write /sys/fs/cgroup/cpuset .... /cpuset.mems:
numerical result out of range"": unknown
```

Note, in the future we may want to have a vCPU to guest CPU mapping and
still include the cpuset.Cpus. Until we have this support, clear this as
well.

Fixes: kata-containers#2176
Depends-on: github.com/kata-containers/tests#2846

Signed-off-by: Eric Ernst <[email protected]>
fidencio pushed a commit to fidencio/kata-runtime that referenced this issue Sep 11, 2020
@egernst @fidencio
cpuset: don't set cpuset.mems in the guest
73b5376 
Kata doesn't map any numa topologies in the guest. Let's make sure we
clear the Cpuset fields before passing container updates to the
guest. Without this, we could encounter a runtime failure:

```
process_linux.go:297: applying cgroup configuration for process caused
"failed to write 0,1 to cpuset.mems: writea 0,1 to cpuset.mems: write
0,1 to cpuset.mems: write /sys/fs/cgroup/cpuset .... /cpuset.mems:
numerical result out of range"": unknown
```

Note, in the future we may want to have a vCPU to guest CPU mapping and
still include the cpuset.Cpus. Until we have this support, clear this as
well.

Fixes: kata-containers#2176
Depends-on: github.com/kata-containers/tests#2846

Signed-off-by: Eric Ernst <[email protected]>
chavafg pushed a commit to chavafg/runtime-1 that referenced this issue Oct 16, 2020
@egernst @chavafg
cpuset: don't set cpuset.mems in the guest
fec5580 
Kata doesn't map any numa topologies in the guest. Let's make sure we
clear the Cpuset fields before passing container updates to the
guest. Without this, we could encounter a runtime failure:

```
process_linux.go:297: applying cgroup configuration for process caused
"failed to write 0,1 to cpuset.mems: writea 0,1 to cpuset.mems: write
0,1 to cpuset.mems: write /sys/fs/cgroup/cpuset .... /cpuset.mems:
numerical result out of range"": unknown
```

Note, in the future we may want to have a vCPU to guest CPU mapping and
still include the cpuset.Cpus. Until we have this support, clear this as
well.

Fixes: kata-containers#2176
Depends-on: github.com/kata-containers/tests#2846

Signed-off-by: Eric Ernst <[email protected]>
(cherry picked from commit b5b8870)
jcvenegas pushed a commit to jcvenegas/runtime that referenced this issue Oct 19, 2020
@egernst @jcvenegas
cpuset: don't set cpuset.mems in the guest
efbb2b4 
Kata doesn't map any numa topologies in the guest. Let's make sure we
clear the Cpuset fields before passing container updates to the
guest. Without this, we could encounter a runtime failure:

```
process_linux.go:297: applying cgroup configuration for process caused
"failed to write 0,1 to cpuset.mems: writea 0,1 to cpuset.mems: write
0,1 to cpuset.mems: write /sys/fs/cgroup/cpuset .... /cpuset.mems:
numerical result out of range"": unknown
```

Note, in the future we may want to have a vCPU to guest CPU mapping and
still include the cpuset.Cpus. Until we have this support, clear this as
well.

Fixes: kata-containers#2176
Depends-on: github.com/kata-containers/tests#2846

Signed-off-by: Eric Ernst <[email protected]>
jcvenegas pushed a commit to jcvenegas/runtime that referenced this issue Oct 19, 2020
@egernst @jcvenegas
cpuset: don't set cpuset.mems in the guest
d98da6c 
Kata doesn't map any numa topologies in the guest. Let's make sure we
clear the Cpuset fields before passing container updates to the
guest. Without this, we could encounter a runtime failure:

```
process_linux.go:297: applying cgroup configuration for process caused
"failed to write 0,1 to cpuset.mems: writea 0,1 to cpuset.mems: write
0,1 to cpuset.mems: write /sys/fs/cgroup/cpuset .... /cpuset.mems:
numerical result out of range"": unknown
```

Note, in the future we may want to have a vCPU to guest CPU mapping and
still include the cpuset.Cpus. Until we have this support, clear this as
well.

Fixes: kata-containers#2176
Depends-on: github.com/kata-containers/tests#2846

Signed-off-by: Eric Ernst <[email protected]>
jcvenegas pushed a commit to jcvenegas/runtime that referenced this issue Oct 20, 2020
@egernst @jcvenegas
cpuset: don't set cpuset.mems in the guest
e8b193a 
Kata doesn't map any numa topologies in the guest. Let's make sure we
clear the Cpuset fields before passing container updates to the
guest. Without this, we could encounter a runtime failure:

```
process_linux.go:297: applying cgroup configuration for process caused
"failed to write 0,1 to cpuset.mems: writea 0,1 to cpuset.mems: write
0,1 to cpuset.mems: write /sys/fs/cgroup/cpuset .... /cpuset.mems:
numerical result out of range"": unknown
```

Note, in the future we may want to have a vCPU to guest CPU mapping and
still include the cpuset.Cpus. Until we have this support, clear this as
well.

Fixes: kata-containers#2176

Signed-off-by: Eric Ernst <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@egernst egernst

Labels
bug Incorrect behaviour
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

cpuset: don't set cpuset.mems in the guest egernst/runtime
2 participants
@egernst @lauatic