Proxmox VE 5 kernel update at OVH

Marc Ballat

Renowned Member
Dec 28, 2015
38
7
73
56
I would like to know if I can safely upgrade the kernel of my Debian stretch machine @ OVH. They are proposing the following kernel update : amd64 Linux kernel, version 4.9.150-xxxx-std-ipv6-64.

Thanks in advance.

Marc
 
Why do you use an OVH kernel and not the Proxmox VE kernel?
 
I guess not as I am also getting kernel updates from the Proxmox source. I assume that I can just comment out the entry in /etc/apt/sources.list.d/ovhkernel.list ?

I just reinstalled Debian and Proxmox 5 on a server that has been running since 2013... It was the first time that I was getting such a kernel upgrade proposed. Turned it down.

Marc
 
Post the output of:

> pveversion -v

So you can see which kernel is installed and running.
 
I am using Webmin and didn't notice that in the list of packages to update there was at the same time the Proxmox kernel. I had unchecked the OVH one so that my host has just been upgraded to pve-kernel-4.15 as you can see below.

Thx

# pveversion -v
proxmox-ve: 5.3-1 (running kernel: 4.15.18-9-pve)
pve-manager: 5.3-8 (running version: 5.3-8/2929af8e)
pve-kernel-4.15: 5.3-1
pve-kernel-4.15.18-10-pve: 4.15.18-32
pve-kernel-4.15.18-9-pve: 4.15.18-30
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: not correctly installed
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-3
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-43
libpve-guest-common-perl: 2.0-19
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-36
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-2
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-22
pve-cluster: 5.0-33
pve-container: 2.0-33
pve-docs: 5.3-1
pve-edk2-firmware: 1.20181023-1
pve-firewall: 3.0-17
pve-firmware: 2.0-6
pve-ha-manager: 2.0-6
pve-i18n: 1.0-9
pve-libspice-server1: 0.14.1-1
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 3.10.1-1
qemu-server: 5.0-45
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
 
Looks good, but you miss a reboot to activate kernel pve-kernel-4.15.18-10-pve.