*** MAKE SURE ALL CONTAINERS AND QEMU vms ARE SHUTDOWN ***
*** MAKE BACKUP OF ALL CONTAINERS AND QEMU VMS ***
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-96pve-kernel-2.6.32-33-pve: 2.6.32-138pve-kernel-2.6.32-26-pve: 2.6.32-114pve-kernel-2.6.32-18-pve: 2.6.32-88lvm2: 2.02.98-pve4clvm: 2.02.98-pve4corosync-pve: 1.4.7-1openais-pve: 1.1.4-3libqb0: 0.11.1-2redhat-cluster-pve: 3.2.0-2resource-agents-pve: 3.9.2-4fence-agents-pve: 4.0.10-1pve-cluster: 3.0-15qemu-server: 3.3-1pve-firmware: 1.1-3libpve-common-perl: 3.0-19libpve-access-control: 3.0-15libpve-storage-perl: 3.0-25pve-libspice-server1: 0.12.4-3vncterm: 1.1-8vzctl: 4.0-1pve6vzprocps: 2.0.11-2vzquota: 3.1-2pve-qemu-kvm: 2.1-10ksm-control-daemon: 1.1-1glusterfs-client: 3.5.2-1
No comments:
Post a Comment