LXC container shows the same LA as the host

D

DmytroKhytryi

Member
Nov 26, 2021
5
0
6
40
System packages:

Code: 
root@:~# pveversion -v
proxmox-ve: 7.3-1 (running kernel: 5.15.74-1-pve)
pve-manager: 7.3-4 (running version: 7.3-4/d69b70d4)
pve-kernel-helper: 7.3-3
pve-kernel-5.15: 7.3-1
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.13.19-6-pve: 5.13.19-15
ceph-fuse: 14.2.21-1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.3
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.3-1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-2
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.3-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.3.2-1
proxmox-backup-file-restore: 2.3.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.0-1
proxmox-widget-toolkit: 3.5.3
pve-cluster: 7.3-2
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.6-3
pve-ha-manager: 3.5.1
pve-i18n: 2.8-2
pve-qemu-kvm: 7.1.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.9-pve1


"-l" flag is already added to lxcfs service with "systemctl edit lxcfs":

Code: 
[Service]
ExecStart=
ExecStart=/usr/bin/lxcfs -l /var/lib/lxcfs/


Results:


Code: 
root@:~# systemctl show lxcfs | grep ExecStart
ExecStart={ path=/usr/bin/lxcfs ; argv[]=/usr/bin/lxcfs -l /var/lib/lxcfs/ ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
ExecStartEx={ path=/usr/bin/lxcfs ; argv[]=/usr/bin/lxcfs -l /var/lib/lxcfs/ ; flags= ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
root@:~#


Using Enterprise repository with an active subscription.

And still LA in CT shows the same as on host.
Click to expand...
 
- as for LA, yes.
- as for container reboot, yes.

Code: 
root@:~# cat /proc/loadavg
2.22 2.10 1.92 1/3709 2841290
root@proxmox1:~# pct enter 4444
[root@test ~]# cat /proc/loadavg
2.28 2.12 1.92 2/3719 2841846
[root@uk0948test ~]# exit
root@:~# cat /proc/loadavg
2.28 2.12 1.92 2/3724 2841857
root@:~#
 
Did you reboot your system inbetween? That would be the easiest way to ensure everything gets reloaded and restarted
With only restarting the lxc, it didn't always work for me.
 
You must log in or register to reply here.
Top Bottom