Pre-upgrade considerations
- In the test environment, correct and then upgrade to a production environment (Freeze upgrade all right, unless foolproof).
- Production environment upgrade, be sure to do a backup, in case Ben collapse, and have a chance to be reborn.
Update Readiness
This process only needs to change about the software update source operative to modify the file /etc/apt/sources.list, add the following line:
deb http://download.proxmox.com/debian stretch pve-no-subscription
Save changes, and to determine what the current proxmox VE version number, the command is:
root@pve:/etc/apt# pveversion -v
proxmox-ve: 5.3-1 (running kernel: 4.15.18-9-pve)
pve-manager: 5.3-5 (running version: 5.3-5/97ae681d)
pve-kernel-4.15: 5.2-12
pve-kernel-4.15.18-9-pve: 4.15.18-30
corosync: 2.4.4-pve1
………省略……
root@pve:/etc/apt# pveversion -v
proxmox-ve: 5.3-1 (running kernel: 4.15.18-9-pve)
pve-manager: 5.3-5 (running version: 5.3-5/97ae681d)
pve-kernel-4.15: 5.2-12
pve-kernel-4.15.18-9-pve: 4.15.18-30
corosync: 2.4.4-pve1
......... omitted ......
To perform the update
Command line apt-get update && apt-get dist-upgrade, look at the output, understand the update process.
Verify the upgrade
See Ø command line: pveversion -v, the output shown below.
Ø Proxmox web management background view.
The output from the update, you can also see the kernel update. To enable the new kernel, reboot the system can be considered. Before restarting the system, take a look at the system running kernel:
root@pve:/etc/apt# uname -ar
Linux pve 4.15.18-9-pve #1 SMP PVE 4.15.18-30 (Thu, 15 Nov 2018 13:32:46 +0100) x86_64 GNU/Linux
Reboot the system, and then check the kernel version:
root@pve:~# uname -ar
Linux pve 4.15.18-18-pve #1 SMP PVE 4.15.18-44 (Wed, 03 Jul 2019 11:19:13 +0200) x86_64 GNU/Linux
It can be seen, we do use the new kernel.