Downloads

From Proxmox VE
Revision as of 11:38, 21 January 2010 by Martin (talk | contribs)
Jump to navigation Jump to search

Proxmox Virtual Environment 1.5 (ISO Image)

Release notes: Roadmap#Proxmox_VE_1.5

Download the ISO image, burn it to CD-ROM and boot your server from CD-ROM. For details see Installation

(MD5SUM for the ISO is 9933270f21eebdd1fb8d2bdd2085d059)

Update a running Proxmox Virtual Environment 1.4 to 1.5

Update your repository and packages:

apt-get update

If you get any errors, your sources.list (or your network) has a problem. Before you update your system, you should stop all your running VM´s.

Now you can install the new Proxmox VE virtual package:

apt-get upgrade && apt-get install proxmox-ve-2.6.18

(alternative: proxmox-ve-2.6.24 or proxmox-ve-2.6.32)

Now, check the bootloader grub to make sure that the system boots the right kernel.

nano /boot/grub/menu.lst

Finally reboot into your new kernel and check if you got the latest Proxmox VE packages with 'pveversion -v':

pveversion -v

pve-manager: 1.5-5 (pve-manager/1.5/4627)
running kernel: 2.6.18-1-pve
proxmox-ve-2.6.18: 1.5-4
pve-kernel-2.6.24-9-pve: 2.6.24-18
pve-kernel-2.6.18-1-pve: 2.6.18-4
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-7
vncterm: 0.9-2
vzctl: 3.0.23-1pve5
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-4

Proxmox Virtual Environment 1.4 (ISO Image)

Release notes: Roadmap#Proxmox_VE_1.4

Download the ISO image, burn it to CD-ROM and boot your server from CD-ROM. For details see Installation

(MD5SUM for the ISO is 0bef854dcca1718f73ff64e383df280a)

Update a running Proxmox Virtual Environment 1.2 or 1.3 to 1.4

Update your repository and packages:

apt-get update

If you get any errors, your sources.list (or your network) has a problem. Before you update your system, you should stop all your running VM´s.

Now you can install the new software packages (incl. Kernel):

apt-get dist-upgrade

Finally reboot and check if you got the latest Proxmox VE packages:

Kernel version:

uname -a

Expected output: 
2.6.24-8-pve #1 SMP PREEMPT Fri Oct 16 11:17:55 CEST 2009 x86_64 GNU/Linux

PVE Manager version:

pveversion -v

Expected output:

pve-manager: 1.4-9 (pve-manager/1.4/4390)
qemu-server: 1.1-6
pve-kernel: 2.6.24-16
pve-qemu-kvm: 0.11.0-2
pve-firmware: 1
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.2-3
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1

Update a running Proxmox Virtual Environment 1.1 to 1.4

Proxmox VE 1.4 is based on Debian Lenny (1.1 is based on Etch). Therefore the update is a major distribution upgrade (about 200 mb) and you should take some basic steps:

  • make sure you have a working backup of your virtual machines (see Backup - Restore - Live Migration)
  • its recommended to stop all running virtual machines before executing the update script

Note: If you got a custom installation (e.g. from your hosting provider like OVH) you should contact your provider for update instructions.

To perform the update, please log in via ssh or via console:

wget http://pve.proxmox.com/debian/dists/lenny/pve-upgrade-1.1-to-1.4

chmod +x pve-upgrade-1.1-to-1.4

./pve-upgrade-1.1-to-1.4

The script updates your system in several steps automatically to Proxmox VE 1.4. If you got any errors, correct them and run the script again.

Optional: after the successful upgrade you can purge all unnecessary package. Only do this if you have not installed any additional packages - else they will get removed. This is just to save space on the harddisk.

./pve-upgrade-1.1-to-1.4 --purge

Finally reboot and check if you got the latest Proxmox VE packages.

Kernel version:

uname -a

Expected output: 
2.6.24-8-pve #1 SMP PREEMPT Fri Oct 16 11:17:55 CEST 2009 x86_64 GNU/Linux

PVE Manager version:

pveversion -v

Expected output:

pve-manager: 1.4-9 (pve-manager/1.4/4390)
qemu-server: 1.1-6
pve-kernel: 2.6.24-16
pve-qemu-kvm: 0.11.0-2
pve-firmware: 1
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.2-3
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1

This script is tested and working for the standard Proxmox VE 1.1 installation.

Proxmox Virtual Environment 1.4 beta2

Release notes: Roadmap#Proxmox_VE_1.4_beta2

This is the second beta release and therefore not intended for production systems.

Download the ISO image, burn it to CD-ROM and boot your server from CD-ROM. For details see Installation

(MD5SUM is 57e9761172775bee6ccb32ae6528a742)

Proxmox Virtual Environment 1.4 beta1 (ISO Image updated on 17.9.2009)

Release notes: Roadmap#Proxmox_VE_1.4_beta1

This is a beta release and therefore not intended for production systems.

Download the ISO image, burn it to CD-ROM and boot your server from CD-ROM. For details see Installation

(MD5SUM is 26d4e456dd306b0ad5ecef897205134e)

Update a running Proxmox Virtual Environment 1.3 to 1.4beta1 or 1.4beta2

Change your sources.list to use the pvetest repositories:

Note: This is a beta release and therefore not intended for production systems.

nano /etc/apt/sources.list
deb http://ftp.debian.org/debian lenny main contrib

# PVE packages provided by proxmox.com
deb http://download.proxmox.com/debian lenny pvetest

# security updates
deb http://security.debian.org/ lenny/updates main contrib

Update your repository and packages:

apt-get update

apt-get dist-upgrade

And finally reboot into the new Kernel.

Proxmox Virtual Environment 1.3 (ISO Image)

Release notes: Roadmap#Proxmox_VE_1.3

Download the ISO image, burn it to CD-ROM and boot your server from CD-ROM. For details see Installation

(MD5SUM is 6ddefdba42121ea24b4e1a3b17d93355)

Important note

If you run windows KVM guests your operating system will recognize some hardware changes on the first boot and windows shows a new network card in the device manager. (e.g. you need to reassign the fixed IP setup to the new network card. if you have DHCP setup there should be no issues). Under some circumstances reactivation of your windows license can be necessary.

Update a running Proxmox Virtual Environment 1.2 to 1.3

Update your repository and packages:

apt-get update

If you get any errors, your sources.list (or your network) has a problem. Before you update your system, you should stop all your running VM´s.

Now you can install the new software packages (incl. Kernel):

apt-get dist-upgrade

Finally reboot and check if you got the latest Proxmox VE packages:

Kernel version:

uname -a

Expected output:

... 2.6.24-7-pve #1 SMP PREEMPT Tue Jun 2 08:00:29 CEST 2009 x86_64 GNU/Linux

PVE Manager version:

pveversion -v

Expected output: 

pve-manager: 1.3-1 (pve-manager/1.3/4023)
qemu-server: 1.0-14
pve-kernel: 2.6.24-8
pve-kvm: 86-1
pve-firmware: 1
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.1-2
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1


Proxmox Virtual Environment 1.2 (ISO Image)

Release notes: Roadmap#Proxmox_VE_1.2

Download the ISO image, burn it to CD-ROM and boot your server from CD-ROM. For details see Installation

(MD5SUM is 005e9c0297ff1eb21e37c33c51ba6c7e)

Update a running Proxmox Virtual Environment 1.1 to 1.2

Proxmox VE 1.2 is the first release based on Debian Lenny. Therefore the update is a major distribution upgrade (about 200 mb) and you should take some basic steps:

  • make sure you have a working backup of your virtual machines (see Backup - Restore - Live Migration)
  • its recommended to stop all running virtual machines before executing the update script

Note: If you got a custom installation (e.g. from your hosting provider like OVH) you should contact your provider for update instructions. For OVH, see these additional update instructions.

To perform the update, please log in via ssh or via console:

wget http://pve.proxmox.com/debian/dists/lenny/pve-upgrade-1.1-to-1.2

chmod +x pve-upgrade-1.1-to-1.2

./pve-upgrade-1.1-to-1.2

The script updates your system in several steps automatically to Proxmox VE 1.2. If you got any errors, correct them and run the script again.

Optional: after the successful upgrade you can purge all unnecessary package. Only do this if you have not installed any additional packages - else they will get removed. This is just to save space on the harddisk.

./pve-upgrade-1.1-to-1.2 --purge

Finally reboot and check if you got the latest Proxmox VE packages.

Kernel version:

uname -a

Expected output: 
2.6.24-5-pve #1 SMP PREEMPT Tue May 12 09:01:17 CEST 2009 x86_64 GNU/Linux

PVE Manager version:

pveversion -v

Expected output:

pve-manager: 1.2-1 (pve-manager/1.2/3982)
qemu-server: 1.0-12
pve-kernel: 2.6.24-6
pve-kvm: 85-1
pve-firmware: 1
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.1-1
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1

This script is tested and working for the standard Proxmox VE 1.1 installation.

Proxmox Virtual Environment 1.1 (ISO Image)

Release notes: Roadmap#Proxmox_VE_1.1

Download the ISO image, burn it to CD-ROM and boot your server from CD-ROM. For details see Installation

(MD5SUM is 5d2962db353716415fb07067d61f90bc)

Update a running Proxmox Virtual Environment V 1.x to the latest version

These instructions should be used for all standard Proxmox VE 1.x installations.

Note: If you got a custom installation (e.g. from your hosting provider like OVH) you should contact your provider for update instructions.


Update your repository and packages:

apt-get update

If you get any errors, your sources.list (or your network) has a problem. Before you update your system, you should stop all your running VM´s.

Now you can install the new software packages (incl. Kernel):

apt-get dist-upgrade

Finally reboot and check if you got the latest Proxmox VE packages:

Kernel version:

uname -a

Expected output: 
2.6.24-2-pve #1 SMP PREEMPT Wed Jan 14 11:32:49 CET 2009 x86_64 GNU/Linux

PVE Manager version:

pveversion -v

Expected output: 

pve-manager: 1.1-1 (pve-manager/1.1/3675)
qemu-server: 1.0-7
pve-kernel: 2.6.24-5
pve-kvm: 83-1
pve-firmware: 1
vncterm: 0.9-1
vzctl: 3.0.23-1pve1
vzdump: 1.1-1
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1dso1

Note: If you start existing Windows KVM VM´s, the Windows OS finds some new hardware pieces and install automatically new driver - and needs a reboot then.

Proxmox Virtual Environment 1.0 (ISO Image)

Release notes: Roadmap#Proxmox_VE_1.0

Download the ISO image, burn it to CD-ROM and boot your server from CD-ROM. For details see Installation

(MD5SUM is fdd5b603d3e9558f125edfc55dcfb3ef)

Update a running Proxmox Virtual Environment V0.9beta2

These instructions should be used for all standard Proxmox VE 0.9beta2 installations.

Note: If you still run 0.9, please stop all running VM and remove the following package before proceeding.

dpkg -r pve-kvm-2.6.24

Note: If you got a custom installation (e.g. from your hosting provider like OVH) you should contact your provider for update instructions.

Review and correct the sources.list

We changed the repositories so you need to correct your list.

nano /etc/apt/sources.list
deb http://ftp.debian.org/debian etch main

# PVE packages provided by proxmox.com
deb http://download.proxmox.com/debian etch pve

# security updates
deb http://security.debian.org/ etch/updates main

Add the Proxmox VE repository key:

wget -O- "http://download.proxmox.com/debian/key.asc" | apt-key add -

Update your repository and install the new packages

apt-get update

If you get any errors, your sources.list (or your network) has a problem.

Before you update your system, you should stop all your running VM´s.

apt-get dist-upgrade

Update the list of Virtual Appliances:

pveam update

We changed the boot loader from lilo to grub, so you need to install grub:

mkdir /boot/grub

apt-get install grub

Now you can install the new Kernel:

apt-get install proxmox-ve pve-kernel

Install grub into the MBR to use the new Kernel:

grub-install hd0

Finally reboot and check if you got the latest Proxmox VE packages:

Kernel version:

uname -a

Expected output: 2.6.24-1-pve #1 SMP PREEMPT Fri Oct 24 11:34:13 CEST 2008 x86_64 GNU/Linux (or newer)

PVE Manager version:

pveversion -v

Expected output: 

pve-manager: 1.0-2 (pve-manager/1.0/3399)
qemu-server: 1.0-1
pve-kernel: 2.6.24-4
pve-kvm: 75-1
pve-firmware: 1
vncterm: 0.9-1
vzctl: 3.0.22-3pve3
vzdump: 1.1-1
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1dso1

Configure your Proxmox VE via the Central Web-based Management