Failed to set "cpu.weight" to "0"

LXD
1

Hello,

After a move of this container from a host to an other host, I can’t start it anymore on the new host:

lxc info --show-log vm739943

Name: vm739943
Location: none
Remote: unix://
Architecture: x86_64
Created: 2021/01/17 04:22 UTC
Status: Stopped
Type: container
Profiles: default

Log:

lxc vm739943 20210117111705.577 ERROR cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2957 - Numerical result out of range - Failed to set “cpu.weight” to “0”
lxc vm739943 20210117111705.577 ERROR start - start.c:lxc_spawn:1756 - Failed to setup cgroup limits for container “vm739943”
lxc vm739943 20210117111705.577 ERROR lxccontainer - lxccontainer.c:wait_on_daemonized_start:859 - Received container state “ABORTING” instead of “RUNNING”
lxc vm739943 20210117111705.577 ERROR start - start.c:__lxc_start:1999 - Failed to spawn container “vm739943”
lxc vm739943 20210117111705.577 WARN start - start.c:lxc_abort:1012 - No such process - Failed to send SIGKILL via pidfd 18 for process 10618
lxc 20210117111705.607 WARN commands - commands.c:lxc_cmd_rsp_recv:124 - Connection reset by peer - Failed to receive response for command “get_state”

lxc/lxd version is 4.8.

Any idea ?

Thank you !

2

What does lxc config show --expanded vm739943 look like?

3

lxc config show --expanded vm739943

architecture: x86_64
config:
image.architecture: amd64
image.description: Debian stretch amd64 (20201222_05:24)
image.os: Debian
image.release: stretch
image.serial: “20201222_05:24”
image.type: squashfs
image.variant: default
limits.cpu: “4”
limits.cpu.allowance: 0%
limits.cpu.priority: “0”
limits.memory: 32GB
limits.memory.swap: “false”
limits.processes: “5000”
volatile.base_image: 9883f71b36e95b989efaae8d43e8003a4572d7bb8e3ecec53330b240feef4e79
volatile.eth0.host_name: veth203800c4
volatile.eth0.hwaddr: 00:16:3e:bf:f4:72
volatile.idmap.base: “0”
volatile.idmap.current: ‘[{“Isuid”:true,“Isgid”:false,“Hostid”:1000000,“Nsid”:0,“Maprange”:65536},{“Isuid”:false,“Isgid”:true,“Hostid”:1000000,“Nsid”:0,“Maprange”:65536}]’
volatile.idmap.next: ‘[{“Isuid”:true,“Isgid”:false,“Hostid”:1000000,“Nsid”:0,“Maprange”:65536},{“Isuid”:false,“Isgid”:true,“Hostid”:1000000,“Nsid”:0,“Maprange”:65536}]’
volatile.last_state.idmap: ‘[{“Isuid”:true,“Isgid”:false,“Hostid”:1000000,“Nsid”:0,“Maprange”:65536},{“Isuid”:false,“Isgid”:true,“Hostid”:1000000,“Nsid”:0,“Maprange”:65536}]’
volatile.last_state.power: STOPPED
volatile.uuid: 92577a9d-2e8c-42a7-955f-2f4d4dfdbb46
devices:
eth0:
name: eth0
network: lxdbr0
type: nic
root:
path: /
pool: default
size: 10GB
type: disk
ephemeral: false
profiles:

  • default
    stateful: false
    description: “”

    limits.cpu.allowance: 0%
    limits.cpu.priority: “0”
    I don’t know how this came into the equation.
    I changed it to non-zero and now it starts fine.
    Thank you !