NOFILE soft limit

[adamb]

@fiona

Would it be possible to clarrify this patch for us?

https://lists.proxmox.com/pipermail/pve-devel/2023-December/061043.html

We have a enviroment that is pushing the limits with NOFILE.

root@proxhost1:~# for pid in $(pidof kvm); do prlimit -p $pid | grep NOFILE; ls -1 /proc/$pid/fd/ | wc -l; done
NOFILE max number of open files 1024 1048576 files
1023

Am I correct in thinking that the soft limit should auto bump to the hard limit if the processes requires it?

root@proxhost1:~# pveversion
pve-manager/7.4-18/b1f94095 (running kernel: 5.15.152-1-pve)

 

[fiona]

Hi,
yes, the patch increases the soft limit up to the configured hard limit during start of the QEMU process. But the patch is present in pve-qemu-kvm >= 8.1.5-3, so not in Proxmox VE 7. Proxmox VE 7 will be end-of-life in 1.5 months, please consider upgrading: https://pve.proxmox.com/wiki/Upgrade_from_7_to_8

 

[adamb]

Hi,
yes, the patch increases the soft limit up to the configured hard limit during start of the QEMU process. But the patch is present in pve-qemu-kvm >= 8.1.5-3, so not in Proxmox VE 7. Proxmox VE 7 will be end-of-life in 1.5 months, please consider upgrading: https://pve.proxmox.com/wiki/Upgrade_from_7_to_8

I appreciate the quick response.

The bug report shows this being back ported to version 7?

 

[Neobin]

The bug report shows this being back ported to version 7?

No. This only means to which version the ticket initially referred to; respectively to which version it currently refers to, if it is still relevant in a newer version, because (any)one could simply update that field (from e.g.: 7 to: 8). (But this is, like in this case, not done everytime.)