CloudLinux now supports cgroup v2 on CloudLinux 8, 9, 10, and Ubuntu 22. New installations of CloudLinux 10 following this release will use cgroup v2 by default. On all other versions, cgroup v1 remains the default, and you can switch to v2 when you’re ready.
From a day-to-day operations standpoint, practically nothing changes. Your LVE limits, control panel interface, and resource monitoring all continue to work the same way.
Why cgroup v2 matters
Contents
cgroup (control groups) is the Linux kernel mechanism that CloudLinux builds on to enforce per-user resource limits. The Linux kernel has two versions of this mechanism: v1 and v2.
cgroup v2 has been the default in major Linux distributions since RHEL 9, Ubuntu 22.04, and Debian 11, and remains so in all current releases. Active kernel development focuses on v2, and it is the recommended interface for new deployments.
For the technically curious, the official Linux kernel cgroup v2 documentation covers the full specification.
What changes for CloudLinux users
Almost nothing from a user perspective. CloudLinux’s resource isolation (LVE) works the same way it always has: per-user CPU, memory, I/O, and process limits are enforced transparently.
The one notable change is that under cgroup v2, memory and swap are managed separately by the kernel rather than as a combined limit. In normal operation, this makes no practical difference. The only scenario where behavior differs is during server-wide memory exhaustion, where the kernel handles swap differently. If your environment is sensitive to this, cgroup v1 remains available as a fallback.
Supported versions
cgroup v2 is supported on CloudLinux 8, 9, 10, and Ubuntu 22.
The following package versions are required:
| Package | CloudLinux 8 | CloudLinux 9 | CloudLinux 10 | Ubuntu 22 |
| kmod-lve / kmodlve-dkms | 2.1-58+ | 2.1-58+ | 2.1-58+ | 2.1-58+ |
| tuned-profiles-cloudlinux | 0.2-14+ | 0.2-15+ | 0.3-6+ | 0.2-10+ |
CloudLinux 7 is not supported.
How to enable cgroup v2
Switching between cgroup versions is done by applying the appropriate tuned profile and rebooting. Choose the profile that matches your current profile family.
If you use the default profile:tuned-adm profile cloudlinux-default-cgv2rebootIf you use the latency-performance profile:
tuned-adm profile cloudlinux-latency-performance-cgv2reboot
How to verify cgroup v2 is active
After rebooting, check with the following command:
(mount | grep cgroup2 -q && test -d /sys/module/kmodlve && echo OK) || echo "NOT OK"
Switching back to cgroup v1
If you need to revert, apply the v1 profile and reboot.
Default profile:
tuned-adm profile cloudlinux-default-cgv1rebootLatency-performance profile:
tuned-adm profile cloudlinux-latency-performance-cgv1reboot
