On a minimal Ubuntu 20.04 server that's just been set up (and with some services disabled), I'm finding that htop is conveying that there's more processor activity going on than what I figure should be happening and I'm not sure if (in this unprivileged LXC container) it's picking up activity from other peer virtual machines and containers or if Ubuntu is just behaving very badly.
Here's a short screencast to illustrate:
I have 16 cores (out of 24 on the server) assigned to this LXC ct.
htop is at version 2.2.0.
config file contents:
lxc.cgroup.relative = 0
lxc.cgroup.dir.monitor = lxc.monitor/101
lxc.cgroup.dir.container = lxc/101
lxc.cgroup.dir.container.inner = ns
lxc.arch = amd64
lxc.include = /usr/share/lxc/config/ubuntu.common.conf
lxc.include = /usr/share/lxc/config/ubuntu.userns.conf
lxc.seccomp.profile = /var/lib/lxc/101/rules.seccomp
lxc.apparmor.profile = generated
lxc.apparmor.allow_nesting = 1
lxc.mount.auto = sys:mixed
lxc.monitor.unshare = 1
lxc.idmap = u 0 100000 65536
lxc.idmap = g 0 100000 65536
lxc.tty.max = 2
lxc.environment = TERM=linux
lxc.uts.name = HOSTNAME
lxc.cgroup2.memory.max = 25769803776
lxc.cgroup2.memory.swap.max = 17179869184
lxc.rootfs.path = /var/lib/lxc/101/rootfs
lxc.net.0.type = veth
lxc.net.0.veth.pair = veth101i0
lxc.net.0.hwaddr = 14:5A:59:1A:BA:25
lxc.net.0.name = eth0
lxc.net.0.script.up = /usr/share/lxc/lxcnetaddbr
lxc.cgroup2.cpuset.cpus = 0-1,3,5,7,9-11,13,15-19,21-22
0 Answers