Update 2: previous statement about updating initramfs is false. System is still swapping.
However, i have located "problem", it seems that proxmox processes, have their own swappiness parameter set (using cgroups), it means, those processes (pvedaemon, pve-ha-cr, pvestatd, pve-firewall, pve-ha-lr, etc) will not honor global swappiness parameter, and this means that those proxmox programs will use swap memory.
If globally is set vm.swappiness=0 then other processes (running virtual KVM machines) will not use swap memory.
However, i have located "problem", it seems that proxmox processes, have their own swappiness parameter set (using cgroups), it means, those processes (pvedaemon, pve-ha-cr, pvestatd, pve-firewall, pve-ha-lr, etc) will not honor global swappiness parameter, and this means that those proxmox programs will use swap memory.
Code:
root@cd03 ~ # cat /proc/sys/vm/swappiness
0
root@cd03 ~ # cat /sys/fs/cgroup/memory/system.slice/pvedaemon.service/memory.swappiness
60
root@cd03 ~ # smem -s swap -r | head -n 12
PID User Command Swap USS PSS RSS
3381 root pvedaemo 91084 204 324 2568
3405 root pve-ha-cr 71712 8592 9814 15012
3385 root pvedaemon worke 67760 11200 18626 39040
3386 root pvedaemon worke 66992 10452 17841 38084
3384 root pvedaemon worke 63756 12020 19657 40292
3234 root /usr/bin/pmxcfs 50496 17680 24925 36280
3357 root pvestat 40952 29428 30783 37096
3356 root pve-firewal 35244 36428 37701 43332
3454 root pve-ha-lr 23544 56384 57645 63136
383 root /lib/systemd/systemd-journa 324 9856 21684 36348
29602 root /usr/bin/kvm -id 120 -chard 0 2098104 2099509 2109448
If globally is set vm.swappiness=0 then other processes (running virtual KVM machines) will not use swap memory.