Upgrade from 4.x to 5.0
- 1 Introduction
- 2 New installation
- 3 In-place upgrade
- 3.1 Preconditions
- 3.2 Move important Virtual Machines and Containers
- 3.3 Actions Step by Step
- 3.4 Troubleshooting
- 3.5 Breaking Changes in 5.0
- 3.6 External links
Proxmox VE 5.x introduces major new features, therefore the upgrade must be carefully planned and tested. Depending on your existing configuration, several manual steps are required, including some downtime. NEVER start the upgrade process without a valid backup and without testing the same in a test lab setup.
If you run a customized installation and/or you installed additional packages, for example for sheepdog, or any other third party packages, you need to make sure that you also upgrade these package to Debian Stretch.
Generally speaking there are two possibilities to move from 4.x to 5.x
- New installation on new hardware (and restore VM´s from backup)
- In-place upgrade via apt, step by step
In both cases you'd better empty the browser's cache after upgrade and reload the GUI page or there is the possibility that you see a lot of glitches.
If you run a PVE 4 cluster it's tested and supported to add a PVE 5 node and migrate your guests to the new host.
Caveats to know before you start
- if using ceph, upgrade your ceph cluster to the Luminous release before you upgrade, following the article Ceph Jewel to Luminous.
- Backup all VMs and containers to external media (see Backup and Restore)
- Backup all files in /etc You will need various files in /etc/pve, as well as /etc/passwd, /etc/network/interfaces, /etc/resolv.conf and others depending on what has been configured from the defaults.
- Install Proxmox VE from ISO (this will wipe all data on the existing host)
- Rebuild the cluster if you had any
- Restore the file /etc/pve/storage.cfg (this will re-map and make available any external media you used for backup)
- Restore firewall configs /etc/pve/firewall/ and /etc/pve/nodes/<node>/host.fw (if relevant)
- Restore full VMs from Backups (see Backup and Restore)
If you feel confortable with the command line, and all your VMs/CTs are one shared storage you can also follow the procedure Bypassing backup and restore when upgrading
In-place upgrades are done with apt-get, so make sure that you are familiar with apt before you start here.
Tip: You can perform a test upgrade and a standalone server first. Install the Proxmox VE 4.4 ISO on testing hardware, then upgrade this installation to the latest minor version of Proxmox VE 4.4 (see Package repositories), copy/create relevant configurations to the test machine to replicate your production setup as closely as possible. Then you can start the upgrade. You can even install Proxmox VE 4.4 in a VM and test the upgrade in this environment.
- upgraded to latest V 4.4
- reliable access to all configured storages
- healthy cluster
- no VM or CT running
- valid backup of all VM (needed if something goes wrong)
- Correct repository configuration
- at least 1GB free disk space at root mount point
- ensure your /boot partition, if any, has enough space for a new kernel (min 60MB) - e.g., by removing old unused kernels (see pveversion -v)
- if using Ceph, you should be already running the Ceph Luminous version, but see the caveat above
Move important Virtual Machines and Containers
If any VMs and CTs need to keep running for the duration of the upgrade, migrate them away from the node that is currently upgraded. A migration of a VM or CT from an older version of Proxmox VE to a newer version will always work. A migration from a newer Proxmox VE version to an older version may work, but is in general not supported. Keep this in mind when planning your cluster upgrade.
Actions Step by Step
All has to be done on each Proxmox VE node's command line (via console or ssh; preferably via console in order to exclude interrupted ssh connections). Again, make sure that you have a valid backup of all CT and VM before you start. Further, no changes to any guest, VM nor CT, should be made during the upgrade process.
Add the PVE repositories to you installation
First make sure that your actual installation has the latest package of the Proxmox VE 4.4 release:
apt-get update && apt-get dist-upgrade
Update the Debian repository entry to stretch.
sed -i 's/jessie/stretch/g' /etc/apt/sources.list
Update the Proxmox VE repository entry to stretch.
sed -i 's/jessie/stretch/g' /etc/apt/sources.list.d/pve-enterprise.list
Add the Proxmox VE repository key:
wget http://download.proxmox.com/debian/proxmox-ve-release-5.x.gpg -O /etc/apt/trusted.gpg.d/proxmox-ve-release-5.x.gpg
More information about Package_Repositories
Replace ceph.com repositories with proxmox.com ceph repositories This step is only necessary if you have a ceph cluster on your PVE installation.
echo "deb http://download.proxmox.com/debian/ceph-luminous stretch main" > /etc/apt/sources.list.d/ceph.list
If there is a backports line then remove it. Currently the upgrade has not been tested when packages from the backports repository are installed.
Update the repositories data:
Upgrade the basic system to Debian Stretch and PVE 5.0
Before you can upgrade the system, you have to remove SysVinit.
apt purge insserv sysv-rc initscripts openrc
Start with this step to get the initial set of upgraded packages:
This action will consume some time - depending on the systems performance, this can take up to 60 min or even more. If you run on SSD, the dist-upgrade can be finished in 5 minutes.
During either of the above, you may be asked to approve of some new packages replacing configuration files. Do with them as you see fit, but they are not relevant to the Proxmox upgrade.
Reboot the system in order to use the new PVE kernel
- Failing upgrade to "stretch"
Make the sure that the repository configuration for stretch is correct.
If there was a network failure and the upgrade has been made partially try to repair the situation with
apt-get -fy install
- Unable to boot due to grub failure
Breaking Changes in 5.0
Default display switched from 'cirrus' to 'std'
The default display is now 'std' (Standard VGA card with Bochs VBE extensions), changed from the 'cirrus' type. Cirrus has security bugs and 'std' is the default since qemu 2.2
To still be able to simply live migrate VMs to another PVE 4, or an already upgraded PVE 5 host - without off time, ensure that your Proxmox VE 4 Node is up to date, i.e. you ran an:
apt update apt full-upgrade
cycle, with valid Debian Jessie and Proxmox VE 4 repositories configured!
If you are using older package versions, for example qemu-server older than version 4.0-111, you will run into problems!