Saturday, January 24, 2015

Upgrade Proxmox hardware node from version 2.3.x to 3.1.x

*** MAKE SURE ALL CONTAINERS AND QEMU vms ARE SHUTDOWN ***
*** MAKE BACKUP OF ALL CONTAINERS AND QEMU VMS ***

cd /root


chmod +x pve-upgrade-2.3-to-3.0

./pve-upgrade-2.3-to-3.0

reboot

-----------------------

after reboot confirm to make sure your Proxmox version has been upgraded:

pveversion -v

(for version 3.3-5 - updated on 2014/11/02)

proxmox-ve-2.6.32: 3.3-138 (running kernel: 2.6.32-33-pve)
pve-manager: 3.3-5 (running version: 3.3-5/bfebec03)
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-33-pve: 2.6.32-138
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-1
pve-cluster: 3.0-15
qemu-server: 3.3-1
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-25
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

No comments:

Post a Comment