Proxmox: How to Upgrade from 3.2 to 3.3

1. Login to Proxmox server via SSH or locally
2. # apt-get install dpkg-dev
3. Download latest Proxmox ISO file on a different machine.
4. # mkdir /home/root/downloads
5. Connect to Proxmox server via SCP
a. Navigate to /home/root/downloads
b. Upload ISO to /home/root/downloads
6. # mkdir /media/iso
7. Mount ISO
# mount -o loop /home/root/downloads/<ISO FILE NAME.ISO> /media/iso
8. Create Dists Folder
# mkdir -p /usr/local/mydists/proxmox/debian/dists/wheezy/pve-cd/binary-amd64/
9. Copy Packages from ISO to Dists
# cp /media/iso/proxmox/packages/* /usr/local/mydists/proxmox/debian/dists/wheezy/pve-cd/binary-amd64/
10. Copy the GPG key file on the local Proxmox repo:
# cd /usr/local/mydists/proxmox/debian
# wget -O – | apt-key add –
11. Remove the CD:
# umount /media/iso
12. Navigate to /usr/local/mydists/proxmox/debian/
# cd /usr/local/mydists/proxmox/debian/
# dpkg-scanpackages dists/wheezy/pve-cd/binary-amd64/ /dev/null | gzip > dists/wheezy/pve-cd/binary-amd64/Packages.gz
NOTE: The resulting file, Packages.gz, will finally be inside the folder: /usr/local/mydists/proxmox/debian/dists/wheezy/pve-cd/binary-amd64/
13. # chmod u+x /usr/local/mydists
14. Add deb entry to /etc/apt/sources.list
# nano /etc/apt/sources.list
Add: deb file:/usr/local/mydists/proxmox/debian/dists/wheezy/pve-cd/binary-amd64/ ./
Type: y
Press Enter
15. # apt-get update
16. # apt-get dist-upgrade
17. # reboot
18. Connect to Proxmox server again via SSH
19. Check pveversion
# pveversion -v
18. Navigate to Proxmox web, login, and verify version number 3.3-1

    • SOUISSI Ali
    • September 25th, 2014

    Thanks for this howto there is some corrections 😀

    mount -o loop /home/root/downloads/ /media/iso

    cp /media/iso/proxmox/packages/* /usr/local/mydists/proxmox/debian/dists/wheezy/pve-cd/binary-amd64/

      • xbloodworkx
      • September 25th, 2014

      Thanks, I went through another upgrade this morning and found those as well. I have updated the post to reflect the corrections.

    • Philipp
    • October 15th, 2014

    Many thanks for this guide! – I’ve one additional comment. On my system after these steps I couldn’t switch to HTML5 Console Viewer.
    I had to delete the /etc/apt/sources.list entry for the local files – after next apt-get update and apt-get upgrade one additional packet was installed (fence-agents-pve) – then everything worked as expected.


    • Rob
    • October 21st, 2014

    is it possible to just upgrade over the network and not load and mount an iso file?

      • xbloodworkx
      • October 21st, 2014

      I do not know, didn’t attempt or test that potential option.

    • mcourtois
    • November 2nd, 2014

    Thanks for this howto!

    At step 10, it should be :
    # wget -O – | apt-key add –

      • xbloodworkx
      • November 2nd, 2014

      Thanks Updated!

  1. I had to add pvetest repo

    deb wheezy pve pvetest

    and manyally specify version for fuse

    apt-get install fuse=2.9.2-4 libfuse2=2.9.2-4

    then remove pvetest repository and upgrade

    apt-get dist-upgrade

      • xbloodworkx
      • December 4th, 2014

      I did not run into this issue so I cannot verify, and by no means am I a Proxmox expert, most of this article is copy paste and adjust based on other’s work.

    • Allen
    • December 4th, 2014

    Any idea how to add a local source directly like a mounted CD? Surely the official release CDs would already have a valid packages.gz file, right?

      • xbloodworkx
      • December 4th, 2014

      Check out I hope it helps.

        • Allen
        • December 4th, 2014

        I didn’t actually run into a problem mounting either a CD or a USB flash drive, but I couldn’t get the installation to accept that there was a valid package on the mounted flash drive (where I’d copied the non-free firmware for the Intel wireless adapter.

        This was for a developer’s laptop demo on a Thinkpad T420s, which wouldn’t boot after installing directly from the Proxmox VE 3.3 ISO, whether it was on CD or USB. The initial booting from the media worked fine, but upon completion of installation, a reboot wouldn’t boot to the hard drive AT ALL…

        The only way around that with this system was to boot to & install Debian Wheezy, which would boot from the hard drive after install, and then install Proxmox from the running Debian system. Starting with a netboot/minimal install of Debian, or even the first DVD and a huge install didn’t matter for the wifi drivers/firmware, since it wasn’t included with the distribution – it’s not open source :(, and it was a royal pain to get anything but wifi internet access over the holidays with family, so I couldn’t get very far until I could plug a wire in for a functional network connection…

        If I could find a way to edit the sources.list file to permit an installation to use a mounted CD or a flash drive, I could have both installed my wifi drivers, and actually done a working net install, but without functioning network, everything just ground to a halt.

        I’ve installed Proxmox on other hardware before just fine, so I know that everything I’d need for that is on the Proxmox CD, and I wouldn’t need to grab those files from the internet if I could just convince a Debian system at the command line to accept the mounted CD and the USB flash drive as valid sources.

        I hope this makes more sense now?

        • xbloodworkx
        • December 7th, 2014

        Ahh I would say replace the /usr/local/mydists/proxmox/debian/ with the mount point of you CD rom. You will probably have to dig into the CD to find the specific folders you need to get the full path. As far as the wireless goes I have no clue, sorry.

    • lucas
    • February 24th, 2015

    Migrate from 3.2 to 3.4.

      • xbloodworkx
      • February 25th, 2015

      If I had some Proxmox servers left I would definitely create a new entry. Recently I have started migrating the few Proxmox servers I had to ESXi 5.5.0u2.

  2. I HAVE UPGRADED MY PROXMOX 3.2 to 3.4 using this step and it worked FLOWLESS.

    Thank you, thank you and thank you for your contribution.

  3. vi /etc/apt/sources.list

    # PVE pve-no-subscription repository provided by, NOT recommended for production use
    deb wheezy pve-no-subscription

  4. Hello guys!

    Has anyone ever managed to upgrade to version 5.0?

    Thank you.

  1. January 11th, 2017

Leave a Reply to ASuresh Cancel reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: