Source :

Check your sources.list file, should look like this:

deb wheezy main contrib

# PVE packages provided by

deb wheezy pve

# security updates

deb wheezy/updates main contrib

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 upgrade the packages:

apt-get dist-upgrade

Reboot to activate the new Kernel, to check if you got all packages, run ‘pveversion -v’ and compare your output (all packages should have equal or higher version numbers):

pve-server:~#pveversion -v

proxmox-ve-2.6.32: 3.1-109 (running kernel: 2.6.32-23-pve)

pve-manager: 3.1-3 (running version: 3.1-3/dc0e9b0e)

pve-kernel-2.6.32-23-pve: 2.6.32-109

lvm2: 2.02.98-pve4

clvm: 2.02.98-pve4

corosync-pve: 1.4.5-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.0-1

pve-cluster: 3.0-7

qemu-server: 3.1-1

pve-firmware: 1.0-23

libpve-common-perl: 3.0-6

libpve-access-control: 3.0-6

libpve-storage-perl: 3.0-10

pve-libspice-server1: 0.12.4-1

vncterm: 1.1-4

vzctl: 4.0-1pve3

vzprocps: 2.0.11-2

vzquota: 3.1-2

pve-qemu-kvm: 1.4-17

ksm-control-daemon: 1.1-1

glusterfs-client: 3.4.0-2


Important Note

Due to changes in our repositories you need to update your apt configuration. If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box.

For more details about the Proxmox VE repositories, see Package repositories