Prerequisites and Notes
- Proxmox VE upgrade to the latest stable version 5.4.
- Test environment upgrade.
- If the environment is online, be sure to back up, in case of hang up, have the opportunity to return to the state before the upgrade (PVE 6 stable version did not come out before, production systems do not frivolous).
- Corosync need to upgrade to version 3.X.
Upgrade corosync
If Proxmox VE virtual machine or container is a high-availability configuration (HA), then before upgrading corosync need to close the associated services.
Required to perform the instructions in each node:
systemctl stop pve-ha-lrm && systemctl stop crm
Next, set corosync update source, which is achieved by creating a file. Specific instructions are as follows:
root@pve:~# echo "deb http://download.proxmox.com/debian/corosync-3/ stretch main" > /etc/apt/sources.list.d/corosync3.listThen confirm the validity of the update source changes, the following instruction
root@pve:~# apt-get list --upgradeable
Listing... Done
corosync/stable 3.0.2-pve2~bpo9 amd64 [upgradable from: 2.4.4-pve1]
libcmap4/stable 3.0.2-pve2~bpo9 amd64 [upgradable from: 2.4.4-pve1]
libcorosync-common4/stable 3.0.2-pve2~bpo9 amd64 [upgradable from: 2.4.4-pve1]
libcpg4/stable 3.0.2-pve2~bpo9 amd64 [upgradable from: 2.4.4-pve1]
libqb0/stable 1.0.5-1~bpo9+2 amd64 [upgradable from: 1.0.3-1~bpo9]
libquorum5/stable 3.0.2-pve2~bpo9 amd64 [upgradable from: 2.4.4-pve1]
libvotequorum8/stable 3.0.2-pve2~bpo9 amd64 [upgradable from: 2.4.4-pve1]Seen from the output, it is effective to update the source available. So, do not hesitate to direct updates.
After the update is completed corosync, remember to start pve-ha-larm and pve-ha-crm service at each node.
root@pve:~# systemctl start pve-ha-lrm
root@pve:~# systemctl start pve-ha-crm
If you worry about upgrading affects the business, you can migrate virtual machines or containers to the node on which the other has not been upgraded, and so after the upgrade is good, and then manually migrate back, it will take some time, and the configuration of the specific circumstances of your device are closely related, in particular disk. If you are using a mechanical damn sata disk, then slowly the whole of it!
Ready proxmox VE update source 6
- Confirmed that it is feasible to upgrade type. Proxmox VE 5.4 Proprietary instructions pve5to6, to execute the instruction.
- Change the debian apt sources
Modify the file /etc/apt/sources.list, to "stretch" replaced by "buster".
Ø Add proxmox VE 6 update source.
root@pve:~# echo "deb http://download.proxmox.com/debian/pve buster pvetest" > /etc/apt/sources.list.d/pve-install-repo.list
Ø Change ceph source
root@pve:~# echo "deb http://download.proxmox.com/debian/ceph-luminous buster main" > /etc/apt/sources.list.d/ceph.list
Execution proxmox VE6 update
Command line apt-get update && apt-get dist-upgrade.
Look at output to see which packages have been updated?
Case the update process was computer interaction, pay attention to see output prompt.
Because it is an informal version of the upgrade, so there may be an error in the update process, please disregard. Update process is relatively long, you need to have a little patience. During the upgrade process, proxmox VE's web management background would not normally visit, which is a normal phenomenon (delete the old package, install new, and need to close and restart the service, but the process is automatic).
Verify updated
After the update ends normally, it is best to reboot the system, this will automatically load the new linux kernel upgrade. Login proxmox web management background from a browser, an overview about the major changes in the proxmox VE 6.
Ø check the version number.
Ø View Integrated ceph version (the old version is luminous).
It can be installed directly from the web interface.
