CageFS not supported by kernel

Issue

After disabling LVE_ENABLE in /etc/sysconfig/lve (setting it to no), LVE-related services, including CageFS, fail to start upon server reboot. As a result, features dependent on LVE (such as resource limits and CageFS environments) are non-functional.

cagefs.service: Failed with result 'exit-code'.
Failed to start CageFS service.

Additionally, the LVE kernel module is not loaded:

lsmod | grep kmod
# No output — kernel modules not loaded

Environment

• CageFS
• LVE

Solution

To restore proper LVE and CageFS functionality:

1- Edit the LVE configuration file:

vi /etc/sysconfig/lve

2- Set LVE_ENABLE to yes:

LVE_ENABLE=yes

3- Reboot the server to reinitialize LVE and load the required kernel module.

🔒 Important Note

If you want to remove LVE limits for all users, it is not recommended to disable LVE globally (e.g., by setting LVE_ENABLE=no in /etc/sysconfig/lve), as this can interfere with other CloudLinux features like CageFS.

Instead, the recommended approach is to:

1. Create a hosting package with unlimited LVE limits.

2. Assign this package to the users who should not be restricted by LVE or to all users.

Cause

Setting LVE_ENABLE=no in /etc/sysconfig/lve disables the initialization of the LVE system at boot. This prevents the required kernel module (kmodlve) from being loaded, breaking services that rely on LVE, such as CageFS.