# Live Patching not working **URL:** \ **Category:** SLES Updates\ **Created:** [September 27, 2019, 2:36pm UTC](https://forums.suse.com/t/live-patching-not-working/34409 "2019-09-27T14:36:09Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![sharfuddin](https://avatars.discourse-cdn.com/v4/letter/s/e274bd/32.png) [@sharfuddin](https://forums.suse.com/u/sharfuddin)\ **Post date:** [September 27, 2019, 2:36pm UTC](https://forums.suse.com/t/live-patching-not-working/34409/1 "2019-09-27T14:36:09Z")
Just after installing and registering the system via: `SUSEConnect -e email@address -r SLES_CODE SUSEConnect -p sle-live-patching/12.3/x86_64 -r Live_PATCH_CODE` installed the kgraft: ```auto node2:~ # zypper install kgraft-patch-4_4_73-5-default . . (1/5) Installing: kgraft-1.0-23.9.1.x86_64 .......................................................................................................................[done] (2/5) Installing: wireless-regdb-2019.06.03-4.22.1.noarch ........................................................................................................[done] (3/5) Installing: kernel-default-4.4.73-5.1.x86_64 ...............................................................................................................[done] (5/5) Installing: kgraft-patch-4_4_73-5-default-2-2.3.2.x86_64 ...................................................................................................[done] Output of kgraft-patch-4_4_73-5-default-2-2.3.2.x86_64.rpm %posttrans script: . . ``` And then ```auto node2:~ # zypper install kgraft-patch-4_4_180-94_103-default . . The following 2 NEW packages are going to be installed: kernel-default-4.4.180-94.103.1 kgraft-patch-4_4_180-94_103-default (1/2) Installing: kernel-default-4.4.180-94.103.1.x86_64 .........................................................................................................[done] (2/2) Installing: kgraft-patch-4_4_180-94_103-default-1-4.3.1.x86_64 .............................................................................................[done] ``` i.e the newer kernel(kernel-default-4.4.180-94.103.1) is installed, but still system is running on the old kernel(the one that comes with SLES 12 SP 3 media) running ‘uname -r’ is still showing ` node2:~ # uname -r 4.4.73-7-default ` Output of kgr commands: ```auto node2:~ # kgr status ready node2:~ # kgr patches node2:~ # kgr blocking node2:~ # ``` Please help me know what I am missing, why the latest kernel is not loading ? ---
**Author:** ![Eugen](https://avatars.discourse-cdn.com/v4/letter/e/ebca7d/32.png) [@Eugen](https://forums.suse.com/u/Eugen)\ **Post date:** [September 27, 2019, 5:02pm UTC](https://forums.suse.com/t/live-patching-not-working/34409/2 "2019-09-27T17:02:18Z")
Hi, the safest way is to reboot your system in order to use the newly installed kernel. Regards, Eugen ---
**Author:** ![sharfuddin](https://avatars.discourse-cdn.com/v4/letter/s/e274bd/32.png) [@sharfuddin](https://forums.suse.com/u/sharfuddin)\ **Post date:** [September 27, 2019, 6:06pm UTC](https://forums.suse.com/t/live-patching-not-working/34409/3 "2019-09-27T18:06:04Z")
[QUOTE=eblock;58541]Hi, the safest way is to reboot your system in order to use the newly installed kernel. Regards, Eugen[/QUOTE] Live Patching(Kgraft) is used to apply kernel updates without reboot. Please help me know what I am missing ---
**Author:** ![Andreas1](https://avatars.discourse-cdn.com/v4/letter/a/d26b3c/32.png) [@Andreas1](https://forums.suse.com/u/Andreas1)\ **Post date:** [September 27, 2019, 11:07pm UTC](https://forums.suse.com/t/live-patching-not-working/34409/4 "2019-09-27T23:07:54Z")
The installed kernel version (and SLES Service Pack) is EoL (end of life). The installed kernel version (=\> output of “uname -r”) must be listed on this web page: [https://www.suse.com/products/live-patching/current-patches/](https://www.suse.com/products/live-patching/current-patches/) [https://www.suse.com/lifecycle/](https://www.suse.com/lifecycle/) ---
**Author:** ![Andreas1](https://avatars.discourse-cdn.com/v4/letter/a/d26b3c/32.png) [@Andreas1](https://forums.suse.com/u/Andreas1)\ **Post date:** [September 27, 2019, 11:20pm UTC](https://forums.suse.com/t/live-patching-not-working/34409/5 "2019-09-27T23:20:13Z")
Please read carefully chapter 4 “patch lifecycle” of “Live Kernel Patching Using kGraft”: [https://documentation.suse.com/](https://documentation.suse.com/) ---
**Author:** ![sharfuddin](https://avatars.discourse-cdn.com/v4/letter/s/e274bd/32.png) [@sharfuddin](https://forums.suse.com/u/sharfuddin)\ **Post date:** [October 1, 2019, 8:24am UTC](https://forums.suse.com/t/live-patching-not-working/34409/6 "2019-10-01T08:24:33Z")
On another system where before installing the kgraft, the installed kernel version was ‘4.4.180-94.97’, I installed the: `kgraft-1.0-23.9.1.x86_64 kgraft-patch-4_4_180-94_97-default-3-2.1.x86_64` then reboot the system. Once the system was back(after installing the kgraft), only then again I installed the latest version of kgraft via: `zypper install kgraft-patch-4_4_180-94_103-default ` by running the above command, kernel version 4.4.180-94.102.1 got installed too. The system is almost idle and more than 3 hours are passed but still ‘uname -r’ is showing me the old(4.4.180-94.97) kernel. kgr command gives the following output: [CODE]# kgr status ready # kgr patches kgraft\_patch\_3\_2\_1 # kgr blocking #[/CODE] ---
**Author:** ![Andreas1](https://avatars.discourse-cdn.com/v4/letter/a/d26b3c/32.png) [@Andreas1](https://forums.suse.com/u/Andreas1)\ **Post date:** [October 1, 2019, 6:38pm UTC](https://forums.suse.com/t/live-patching-not-working/34409/7 "2019-10-01T18:38:35Z")
kGraft patches your kernel only “in RAM” (with kgraft-patch\_3\_2\_1). kGraft don’t install any kernel updates “on disk”. If your machine run a supported kernel version, you can safely stay with kGraft on this kernel version until EoL (end of life). With kGraft: =\> the running kernel is fully patched “in RAM”. =\> receive all necessary security updates by kgraft-patch =\> Your kernel images file on hard disc don’t receive any security updates (by kgraft-patch) ---
**Author:** ![sharfuddin](https://avatars.discourse-cdn.com/v4/letter/s/e274bd/32.png) [@sharfuddin](https://forums.suse.com/u/sharfuddin)\ **Post date:** [October 1, 2019, 8:19pm UTC](https://forums.suse.com/t/live-patching-not-working/34409/8 "2019-10-01T20:19:43Z")
[QUOTE=AndreasMeyer;58563]kGraft patches your kernel only “in RAM” (with kgraft-patch\_3\_2\_1). kGraft don’t install any kernel updates “on disk”. If your machine run a supported kernel version, you can safely stay with kGraft on this kernel version until EoL (end of life). With kGraft: =\> the running kernel is fully patched “in RAM”. =\> receive all necessary security updates by kgraft-patch =\> Your kernel images file on hard disc don’t receive any security updates (by kgraft-patch)[/QUOTE] Does it mean that ‘uname -r’ would keep reporting the old kernel ? if so how can I justify Auditors that system is running on patched/updated kernel ? Also does kGraft only address the security bugs i.e only receives the security updates ? or non-security updates too ? ---
**Author:** ![Andreas1](https://avatars.discourse-cdn.com/v4/letter/a/d26b3c/32.png) [@Andreas1](https://forums.suse.com/u/Andreas1)\ **Post date:** [October 2, 2019, 10:36pm UTC](https://forums.suse.com/t/live-patching-not-working/34409/9 "2019-10-02T22:36:09Z")
uname -r reports the actual running kernel. Uname is unaware of the runtime patches from kgraft. So fully correct is: running kernel: \ + [https://en.wikipedia.org/wiki/KGraft](https://en.wikipedia.org/wiki/KGraft) > [@](#): > > Also does kGraft only address the security bugs i.e only receives the security updates ? or non-security updates too ? [https://documentation.suse.com/sles/12-SP4/html/SLES-kgraft/art-kgraft.html#sec-kgraft-scope-patching](https://documentation.suse.com/sles/12-SP4/html/SLES-kgraft/art-kgraft.html#sec-kgraft-scope-patching)