A host kernel fix should not require stopping a shop, database or game server if the correction can take effect while the system is running. TERAMONT now uses live patching to apply compatible fixes in the hypervisor’s memory while its virtual machines keep running. For those updates we do not have to reboot the node or start its guests again.
What changes compared with a hypervisor reboot?
Previously, when we needed to boot a corrected host kernel, our procedure involved restarting the hypervisor and bringing its VMs back up. TERAMONT’s operational estimate for those maintenance events was about 15 to 20 minutes of downtime. That is a historical estimate for our previous procedure, not a universal reboot duration or a measurement from this particular incident.
A compatible live patch changes the decisive step: instead of waiting for the host to boot a replacement kernel, the correction takes effect in the running one. Consider a database inside a VPS: it need not stop and recover from a host reboot for that patch. This illustrates the difference in procedures; it is not a guarantee against every interruption.
Looking for a VPS?
Compare TERAMONT plans and choose the resources your application needs.



What does patching a kernel in memory actually mean?
Installing a kernel package on disk prepares code for a future boot. Live patching lets the running kernel use corrected versions of the functions covered by a patch. Tasks already running have to transition safely. That is why an installed agent, an available patch and an active fix are different states. The release string reported by uname -r can stay the same. Linux kernel documentation on the live patch lifecycle.
When is a maintenance window still necessary?
| Situation | What it means for your VPS |
|---|---|
| A compatible live fix exists for the running host kernel | The fix can take effect without rebooting that hypervisor or its virtual machines for this change. |
| No compatible live fix exists, or a different kernel must be booted | Conventional maintenance remains an option. Not every change can be made in memory. |
| An update is needed inside the VPS | This is independent. Patching the host does not replace a reboot required by the guest’s own kernel. |
What happens after the next reboot?
Patching memory does not by itself change the kernel image the host will boot. After a restart, the important check is that a corrected kernel is running or the compatible live patch is active again. For a specific CVE, ask “Is the fix active on the kernel running now?” rather than “How long has this node been up?”.
A recent example: TERAMONT nodes and the KVM flaw
As of November 20, 2026, we applied the patch for CVE-2026-99312 and none of our nodes remain vulnerable to that flaw. This refers to the hypervisor. It does not mean that your guest OS, plugins or application services have been updated for you. See what CVE-2026-99312 allows on AMD KVM hosts for why the fix belongs on the host.







