High CPU Usage by Proxmox

aniket69

New Member
Aug 3, 2021
5
1
3
27
Hi I restarted my proxmox and suddenly my dedicated server cpu usage is 90-100% i only have 2 lxc running both 1 core 1 gb ram,
My Dedicated Specs are 8 core 16 gb ram please help while doing top there is nothing that is using that much of cpu please help :(
 
  • Like
Reactions: batista10
hi,

please post the output from the following commands:

* pveversion -v

* ps auxfw

* pct config CTID for both containers
 
output of pveversion -v


root@host1:~# pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-1-pve)
pve-manager: 7.0-8 (running version: 7.0-8/b1dbf562)
pve-kernel-5.11: 7.0-3
pve-kernel-helper: 7.0-3
pve-kernel-5.11.22-1-pve: 5.11.22-2
ceph-fuse: 15.2.13-pve1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.0.0-1+pve5
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.1.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-4
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-7
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-2
lxcfs: 4.0.8-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.1-1
proxmox-backup-file-restore: 2.0.1-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.2-4
pve-cluster: 7.0-3
pve-container: 4.0-5
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.2-4
pve-ha-manager: 3.3-1
pve-i18n: 2.4-1
pve-qemu-kvm: 6.0.0-2
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-7
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.4-pve1

output of ps auxfw

output of pct config of vmid 103

Code:
arch: amd64
cores: 1
hostname: newyork1.krakenvpn.com
memory: 1000
nameserver: 8.8.4.4
net0: name=eth0,bridge=vmbr0,gw=142.252.252.129,hwaddr=76:AF:2B:CB:20:15,ip=142.252.252.251/25,type=veth
onboot: 1
ostype: ubuntu
rootfs: local-lvm:vm-103-disk-0,size=10G
searchdomain: 8.8.8.8
swap: 512
unprivileged: 1
lxc.mount.entry: /dev/net/tun dev/net/tun none bind,create=file
output of vm id 1001

Code:
root@host1:~# pct config 1001
arch: amd64
cores: 1
cpulimit: 0
cpuunits: 1024
hostname: test
memory: 1000
nameserver: 8.8.8.8
net0: name=eth0,bridge=vmbr0,hwaddr=00:16:3e:48:41:1f,type=veth
onboot: 1
ostype: ubuntu
rootfs: local-lvm:vm-1001-dufzmu0wbdblol8y-a4hdiup8plioukyu,size=10.000G
swap: 256
 

Attachments

similar issue, I had to restart udev for workaround after reboot

udiskd and udev processes consum many CPU, no dmesg nor errors in log.
Code:
# ps xfa|grep -c systemd-udevd
60

# top -n1|head -n 15
top - 22:01:12 up 2 min,  1 user,  load average: 3.61, 1.75, 0.68
Tasks: 555 total,   3 running, 552 sleeping,   0 stopped,   0 zombie
%Cpu(s):  9.8 us, 10.6 sy,  0.0 ni, 79.6 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :  32099.9 total,  29833.7 free,   1618.7 used,    647.4 buff/cache
MiB Swap:   6144.0 total,   6144.0 free,      0.0 used.  30029.7 avail Mem


    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
    955 root      20   0  393824  12704  10440 R  50.0   0.0   1:20.44 udisksd
    732 root      20   0   22728   4484   3032 S  45.0   0.0   1:03.91 systemd-udevd
    913 message+  20   0   12108   8636   4072 S  45.0   0.0   1:17.50 dbus-daemon
      1 root      20   0  164584  10960   7808 S  35.0   0.0   0:48.17 systemd
    627 root      20   0   22672   5216   3820 S  35.0   0.0   1:00.82 systemd-udevd
    954 root      20   0   13808   7384   6456 S  25.0   0.0   0:29.81 systemd-logind
  10201 root      20   0 9184620 171824  11008 S  15.0   0.5   0:31.73 kvm
    679 root      20   0   22544   4568   3300 S  10.0   0.0   0:15.04 systemd-udevd

after restart udev:
Bash:
systemctl restart udev
# ps xfa|grep -c systemd-udevd
2

top -n1|head -n 11
top - 22:03:03 up 4 min,  1 user,  load average: 3.09, 2.40, 1.06
Tasks: 501 total,   1 running, 500 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.6 us,  0.8 sy,  0.0 ni, 98.6 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :  32099.9 total,  29810.6 free,   1632.8 used,    656.5 buff/cache
MiB Swap:   6144.0 total,   6144.0 free,      0.0 used.  30009.4 avail Mem

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
 107280 root      20   0   13800   4648   3560 R  16.7   0.0   0:00.05 top
  10201 root      20   0 9226768 231408  11008 S   5.6   0.7   0:58.23 kvm
  10566 root      20   0       0      0      0 S   5.6   0.0   0:00.66 vhost-10201
      1 root      20   0  164584  10968   7808 S   0.0   0.0   1:14.71 systemd

Bash:
# pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-5-pve)
pve-manager: 7.0-13 (running version: 7.0-13/7aa7e488)
pve-kernel-helper: 7.1-2
pve-kernel-5.11: 7.0-8
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.5-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve1
libproxmox-acme-perl: 1.3.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-10
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-3
libpve-storage-perl: 7.0-12
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.11-1
proxmox-backup-file-restore: 2.0.11-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.0-10
pve-docs: 7.0-5
pve-edk2-firmware: 3.20210831-1
pve-firewall: 4.2-3
pve-firmware: 3.3-2
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-4
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-16
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1

+1 service to restart daily :-(
Bash:
cat << EOF > /etc/cron.daily/restart_problematic_services
#!/bin/bash

systemctl restart pvestatd
systemctl restart udev
EOF
chmod +x /etc/cron.daily/restart_problematic_services
 
Last edited:
I had the same problem and it turned out to be a hardware problem. Replacing the CPU worked correctly.
Apparently the server did not generate any errors.