A stupid question... but after upgrading to the latest kernel is it necessary to reboot the server?
In most cases; yes.
A stupid question... but after upgrading to the latest kernel is it necessary to reboot the server?
yea , alwaysA stupid question... but after upgrading to the latest kernel is it necessary to reboot the server?
[root@vps1 ~]# uname -ir
3.10.0-714.10.2.lve1.4.79.el7.x86_64 x86_64
[root@vps1 ~]# uptime
06:19:20 up 2 min, 1 user, load average: 0.39, 0.30, 0.12
[root@vps1 ~]# grep -iE "hypervisor|xen|kvm|vmware" /var/log/dmesg --color
[ 0.000000] DMI: Xen HVM domU, BIOS 4.7.2-2.5 05/11/2017
[ 0.000000] Hypervisor detected: Xen HVM
[ 0.000000] Xen version 4.7.
iwl100-firmware.noarch 39.31.5.1-58.el7_4 updates
iwl1000-firmware.noarch 1:39.31.5.1-58.el7_4 updates
iwl105-firmware.noarch 18.168.6.1-58.el7_4 updates
iwl135-firmware.noarch 18.168.6.1-58.el7_4 updates
iwl2000-firmware.noarch 18.168.6.1-58.el7_4 updates
iwl2030-firmware.noarch 18.168.6.1-58.el7_4 updates
iwl3160-firmware.noarch 22.0.7.0-58.el7_4 updates
iwl3945-firmware.noarch 15.32.2.9-58.el7_4 updates
iwl4965-firmware.noarch 228.61.2.24-58.el7_4 updates
iwl5000-firmware.noarch 8.83.5.1_1-58.el7_4 updates
iwl5150-firmware.noarch 8.24.2.2-58.el7_4 updates
iwl6000-firmware.noarch 9.221.4.1-58.el7_4 updates
iwl6000g2a-firmware.noarch 17.168.5.3-58.el7_4 updates
iwl6000g2b-firmware.noarch 17.168.5.2-58.el7_4 updates
iwl6050-firmware.noarch 41.28.5.1-58.el7_4 updates
iwl7260-firmware.noarch 22.0.7.0-58.el7_4 updates
linux-firmware.noarch 20170606-58.gitc990aae.el7_4 updates
microcode_ctl.x86_64 2:2.1-22.5.el7_4 updates