If you run your own CloudLinux server, you may notice that on CloudLinux OS 9 the kernel version no longer contains lve, and there is no "lve kernel" package to install. That is expected. This guide, written for server administrators, explains why and shows how to confirm that LVE (Lightweight Virtual Environment) limits are really working.
From CloudLinux OS 9 onwards, LVE is delivered as a loadable kernel module, kmodlve, on top of a standard kernel, so uname -r shows no lve. That is normal. Check lsmod | grep kmodlve and lvectl list: if the module is loaded and LVEs are listed, LVE is working. If the module is missing, make sure the LVE kernel-module package matches your running kernel and reboot into it.
It applies to a server where you have root access and run CloudLinux yourself. If you have a Domain India shared hosting plan (cPanel, DirectAdmin or Webuzo), you don't manage the kernel or LVE: we do. To see your own account's limits and usage, read Understanding hosting resource limits instead.
1. What changed in CloudLinux OS 9
CloudLinux uses LVE to give every hosting account its own share of CPU, memory, processes and I/O, so one busy site can't slow the whole server down.
On CloudLinux OS 7 and 8, LVE shipped with a CloudLinux-specific kernel, and its version string said so. For example, a CloudLinux 8.10 server we checked on 24 September 2026 reports:
$ uname -r
4.18.0-553.89.1.lve.el8.x86_64On CloudLinux OS 9 and later, CloudLinux no longer rebuilds the kernel for LVE. It ships LVE as a separate kernel module, kmodlve, that loads into the standard kernel. The version string looks like any Enterprise Linux 9 kernel:
$ uname -r
5.14.0-427.20.1.el9_4.x86_64Nothing is broken: the LVE features are the same; only the packaging changed. The module check works on older releases too: the same CloudLinux 8.10 server also lists kmodlve in lsmod, so testing for the module is the one check that works across versions. Any monitoring script or check that decides "LVE is off" because uname -r lacks lve is out of date and should test for the module instead.
2. Check that LVE is active
Run these as root. Each one tests a different layer.
- Confirm the OS release.
cat /etc/redhat-releaseshould name CloudLinux release 9 (or later). - Check the running kernel.
uname -rshows the booted kernel. On a server patched with KernelCare,kcarectl --unameshows the effective, live-patched version. - Check the module is loaded. `lsmodgrep kmodlve
should print a line starting withkmodlve`. The last number is how many things are using it. - Look at the module details.
modinfo kmodlveshows the module's version and the kernel it was built for. - Check LVE is enforcing limits.
lvectl listshows the configured limits, andcat /proc/lve/listlists active LVEs. On a server with hosting accounts, you should see entries for users.
Example of a healthy result:
$ lsmod | grep kmodlve
kmodlve 17657856 2If lsmod shows kmodlve and lvectl list returns limits without errors, LVE is working, whatever the kernel name says.
3. If kmodlve is not loaded
| What you see | Likely cause | What to do |
|---|---|---|
lsmod shows nothing, /proc/lve missing | The module isn't installed for the running kernel | Install or update the LVE kernel-module package, then reboot |
| Module exists but won't load after a kernel update | Kernel and module versions out of step | Update kernel and module together, then reboot into the new kernel |
| Load fails with a signature or key error | Secure Boot rejecting the module | Follow CloudLinux's Secure Boot guidance, or check your firmware settings |
lvectl not found | LVE utilities (lve-utils) not installed | Install CloudLinux's LVE utilities and LVE Manager |
| Everything loads but users see no limits | Limits not set, or the account isn't covered | Check default limits in LVE Manager and lvectl list |
A safe sequence on CloudLinux OS 9:
# see which LVE-related packages are installed
dnf list installed | grep -i lve
# update the kernel and the LVE module together
dnf update
# try loading the module for the running kernel
modprobe kmodlve && lsmod | grep kmodlve
# look for errors
dmesg | grep -i lveIf modprobe fails after a kernel update, reboot into the newest kernel first: the module is built for a specific kernel series, and loading it into an older or unsupported one fails. Package names can differ between CloudLinux releases, so when a name above doesn't match, search with dnf search lve and check CloudLinux's documentation for your version.
Booting a non-CloudLinux kernel, removing the LVE module or blacklisting it removes every account's limits at once, and one heavy site can then slow the whole server. Make kernel changes in a maintenance window, keep the previous kernel in the boot menu, and have console access before you reboot.
4. Related LVE and CageFS errors
- "Failed to initialize LVE library instance" inside a user's shell or a cron job usually points to CageFS or LVE libraries not being ready. See the CageFS jail error guide.
- Resource Limit Is Reached (508) on a site means LVE is working and a limit was hit, not that it's broken. See understanding and troubleshooting the Resource Limit Is Reached error.
- For a wider checklist on cPanel servers, see advanced troubleshooting for CloudLinux and cPanel.
5. Update your monitoring checks
Scripts that look for lve in uname -r give false alarms on CloudLinux OS 9. Test the module instead. A minimal check for a monitoring agent:
#!/bin/sh
# exit 0 if LVE is active, 2 if not
if lsmod | grep -q '^kmodlve'; then
echo "OK: kmodlve loaded"
exit 0
fi
echo "CRITICAL: kmodlve not loaded"
exit 2Run it after every kernel update and reboot, and alert on a non-zero exit.
6. How this relates to Domain India hosting
Our cPanel and DirectAdmin shared hosting servers run CloudLinux with CageFS and LVE limits (CloudLinux 8.10, checked 24 September 2026), and we maintain the kernels, modules and limits. As a shared hosting customer you see the result, not the machinery: your panel shows your CPU, memory and process usage against your plan's limits. See check your hosting resource usage.
If you want to run CloudLinux yourself, you need your own server with root access and a CloudLinux licence. Domain India VPS plans are self-managed KVM servers with full root access; check with support before ordering if you plan to install CloudLinux, so we can confirm it suits the plan and OS image you choose.
- 2 vCPU
- 4 GB DDR4 RAM
- 128 GB NVMe SSD Storage
- 3 TB Monthly Bandwidth
The card price is a Domain India list price on 19 September 2026, excluding 18% GST. See every plan on VPS hosting.
Frequently asked questions
Why doesn't my CloudLinux OS 9 kernel name contain lve?
Because CloudLinux OS 9 delivers LVE as a loadable kernel module, kmodlve, instead of a rebuilt kernel. The kernel version looks like a standard Enterprise Linux 9 kernel, and that is expected.
How do I check that LVE is working on CloudLinux OS 9?
Run lsmod | grep kmodlve to confirm the module is loaded, then lvectl list to confirm limits are configured. If both return results without errors, LVE is active.
Is there still an LVE kernel to install on CloudLinux OS 9?
No. You install the LVE kernel-module package that matches the standard kernel instead. Keep the kernel and the module updated together and reboot into the new kernel after an update.
What should I do if kmodlve won't load?
Update the kernel and the LVE module package together, reboot into the newest kernel, then run modprobe kmodlve and check dmesg for errors. A Secure Boot signature error needs CloudLinux's Secure Boot steps.
Do I need to do anything about LVE on Domain India shared hosting?
No. Domain India manages CloudLinux, LVE and the kernels on its shared servers. You can see your own usage against your plan's limits in your control panel.
Does CloudLinux OS 8 work the same way?
Not quite. CloudLinux OS 8 uses CloudLinux kernels with lve in the version string, for example 4.18.0-553.89.1.lve.el8.x86_64, and also loads the kmodlve module. From CloudLinux OS 9 the lve kernel is gone, so checking for the kmodlve module is the test that works on both.
Ready to check your own server? Run the commands in section 2, or open a support ticket if you're a Domain India customer and your site shows resource-limit errors.
Domain India VPS plans are self-managed KVM servers with full root access, for administrators who run their own software.
See VPS plans