Upgrade from 2.3 to 3.0
There are two possibilities to move from 2.3 to 3.0:
- In-place upgrade via script (recommended)
- New installation on new hardware (and restore VM´s from backup)
In-place upgrade via script
Before you start, make sure you have a valid backup of all your settings, VM´s and CT´s. If the upgrade fails, you should be able to do a clean ISO installations and restore all VM´s and CT´s from backup.
We provide an upgrade script which does the following:
- Dist-upgrade from Squeeze to Wheezy
- Installation of Proxmox VE 3.0
- Optional: Purge obsolete packages
- Up2date Proxmox VE 2.3
- Backup of all VM´s and CT´s
- No running VM´s or CT´s
- Enough free space in your /root file-system
Start the upgrade
- make sure you have up to date 2.3 system
- Login to your Proxmox VE host with SSH and download the script:
- make the script executable:
chmod +x pve-upgrade-2.3-to-3.0
- Stop all your VMs and Containers
The script can download the packages (around 265 MB) before the packages are installed, so this is a good method to minimize downtime, especially if your internet connection is slow.
If you are really ready for the upgrade, run the script:
The script writes a detailed log to 'pve-upgrade.log'.
- Optional: Purge obsolete packages to save disk space (this removes all non default packages, so run this ONLY if you did not installed anything else. Do not run this on customized installations like OVH or similar)
- stop or migrate all VM/CT to another node (live or offline)
- run the upgrade and reboot
- migrate or start the VM/CT on this 3.0 node and check if everything is working as expect. Also live-migrate should work.
- do the same with all other nodes, step by step
Adapt your apt config to get future updates
If you run multipath, you need to adapt your multipath.conf - 'selector' is now called 'path_selector'
GUI/Browser shows old version
Reload the page and/or empty browser cache.
Minor Grub2 issue
Apache2 is not needed anymore and can be removed.
apt-get purge apache2*
Problems on host shutdown
Please remove the 'fuse-utils' package including the init.d script:
apt-get purge fuse-utils insserv
This packages is no longer required, but generate problems because it umounts all fuse file systems very early (including the pve cluster file system mounted at /etc/pve).
Note: The 'insserv' command is neccessary to completely remove the service from the start/stop dependencies (/etc/init.d/.depend.*)
Debian Kernel 3.2 instead of PVE Kernel 2.6.32
If you installed your Proxmox on top of a Debian (and not from the original ISO installer), you will see a Debian 3.2 Kernel being active after upgrade and not a Proxmox 2.6.32-xx-pve. This is simply because Debian Wheezy ships a 3.2 Kernel and due to it's higher version, it gets activated as default kernel.
If OpenVZ doesn't work anymore and you installed PVE on top of Debian, you should find out which Kernel is running:
To remove the Debian Kernel and activate the Proxmox Kernel, do the following:
apt-get purge linux-base
You will get a warning that you're going to remove the running kernel, and that linux-image-* packages will also be removed. You should also reboot as soon as possible to activate the pve Kernel.
New installation on new hardware
Install 3.0 on new servers and move your VM´s step by step via backup/restore. If you choose this method you can do the move step by step and with minimum risk.