Proxmox Virtual Environment 9.0 released!

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
6,649
4,322
315
South Tyrol/Italy
shop.proxmox.com
We are pleased to announce the first stable release of Proxmox Virtual Environment v9.0 - immediately available for download!

The new version is based on the great Debian 13 "Trixie" but we're using a newer Linux kernel 6.14.8-2 as stable default in Proxmox VE.
Beyond the core system updates, we've also refreshed many of our included technologies. You'll find updated versions of essential software like QEMU 10.0.2, LXC 6.0.4, ZFS 2.3.3, and Ceph Squid 19.2.3, all integrated seamlessly.

We're incredibly proud of the hard work that has gone into this release and can't wait for you to experience it.

Some of the exciting new features we've packed into Proxmox VE 9.0:
  • Snapshots as volume chains provide vendor-agnostic support for snapshots on any storage system that supports block storage. This includes iSCSI and Fibre Channel-attached SANs.
  • High-Availability (HA) rules for resource-to-node and resource-to-resource affinity
  • Fabrics for the Software-Defined Networking (SDN) stack
  • Modernized mobile web interface written in the rust programming language using the Yew web framework.
  • Comprehensive upgrade guide from 8 to 9
  • ZFS 2.3.3 with support for adding new devices to RAIDZ pools without downtime
  • and much more

Beyond these major additions, we've also implemented numerous performance enhancements and bug fixes to make your experience even smoother. For a full list of changes, check out our release notes.

Release notes
https://pve.proxmox.com/wiki/Roadmap

Press release
https://www.proxmox.com/en/news/press-releases

Download
https://www.proxmox.com/en/downloads
Alternate ISO download:
https://enterprise.proxmox.com/iso

Documentation
https://pve.proxmox.com/pve-docs

Community Forum
https://forum.proxmox.com

Bugtracker
https://bugzilla.proxmox.com

Source code
https://git.proxmox.com

There has been a lot of feedback from our community members and customers, and many of you reported issues, submitted patches, and were involved in testing - THANK YOU for your support!

FAQ
Q
: Can I upgrade latest Proxmox VE 8 to 9 with apt?
A: Yes, please follow the upgrade instructions on https://pve.proxmox.com/wiki/Upgrade_from_8_to_9

Q: Can I upgrade an 9.0 beta installation to the stable 9.0 via apt?
A: Yes, upgrading from beta to stable installation is possible via apt. We recommend switching to the pve-enterprise repository on upgrade for the most stable experience.

Q: How long will Proxmox VE 8.4 receive bug fixes and security support?
A: Proxmox VE 8.4 will receive security updates and critical bug fixes until August 2026. This support window provides an overlap of approximately one year after the release of Proxmox VE 9.0, giving users ample time to plan their upgrade to the new major version.
For more information on the support lifecycle of Proxmox VE releases, please visit:
https://pve.proxmox.com/pve-docs/chapter-pve-faq.html#faq-support-table

Q: Why is Proxmox VE 9.0 released ahead of the stable Debian 13 release?
A: Debian 13 is scheduled for its stable release this Saturday, August 9. Its core components have been stabilized since it entered the "hard freeze" phase on May 15. Following extensive integration testing and valuable feedback during the Proxmox VE 9.0 beta, we are confident in the stability of this release. Since our core packages are either maintained directly by the Proxmox team or are already locked by Debian's strict freeze policy, there is no technical reason to postpone our release.

Q: Can I install Proxmox VE 9.0 on top of Debian 13 "Trixie"?
A: Yes, see https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie

Q: Can I upgrade my Proxmox VE 8.4 cluster with Ceph Reef to v9.0?
A: This is a two-step process. First, you have to upgrade Ceph from Reef to Squid, and afterward you can upgrade Proxmox VE from 8.4 to 9.0. There are a lot of improvements and changes, so please follow the upgrade documentation exactly as described:
https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid
https://pve.proxmox.com/wiki/Upgrade_from_8_to_9

Q: Where can I get more information about feature updates?
A: Check the roadmap, forum, the mailing list, and/or subscribe to our newsletter.
 
Issue in the upgrade Wiki: The URL for the ceph.sources is not correct for the no-subscription repository. It should be http://download.proxmox.com/debian/ceph-squid instead.
EDIT: I did not find any other issues in a straightforward in-place update from 8.4.8 to 9.0. And it's already fixed. Good work!
EDIT2: A remove VPS also updated without a hitch. Did not even lose the SSH connection via WireGuard running in a container on that server!
EDIT3: vendor-reset is not (yet) compatible with kernel 6.14: https://github.com/gnif/vendor-reset/pull/86
 
Last edited:
Did I understand the upgrade guide correctly that in order to backup pve 9 I also need pbs version 4? In thise case I should probably wait for pbs4 to be released and upgrade to pbs4 first correct?
 
Did I understand the upgrade guide correctly that in order to backup pve 9 I also need pbs version 4? In thise case I should probably wait for pbs4 to be released and upgrade to pbs4 first correct?
For using PVE 9 together with PBS 3 or PVE 8 with future PBS 4 you do not need to wait, we provide full forward and backward compatibility between those releases.

For co-installed PVE and PBS on the same host you need to wait if you want a fully supported PBS 4 release, but if all goes smoothly that shouldn't be an all too long wait;)

FWIW, depending on ones stability criteria one could use the PBS 4 beta for the upgrade:

@ntimo fyi: EDIT: clarified things above, it was worded with mostly the co-installed situation in mind, but being able to backup up to another PBS is not affected at all.
 
Last edited:
When running pve8to9 on a new host I get

Code:
INFO: Check space requirements for RRD migration...
du: cannot access '/var/lib/rrdcached/db/pve2-vm': No such file or directory
command 'du -scb /var/lib/rrdcached/db/pve2-vm' failed: exit code 1
 
When running pve8to9 on a new host I get

Code:
INFO: Check space requirements for RRD migration...
du: cannot access '/var/lib/rrdcached/db/pve2-vm': No such file or directory
command 'du -scb /var/lib/rrdcached/db/pve2-vm' failed: exit code 1
New as in freshly installed with the Proxmox VE 9 ISO? In that case the environment is a bit unexpected for the tool, so such glitches might be present, but it's also not really required to be used as it's mainly for upgrades from PVE 8.
Still, can and should be improved, thanks for your report, we'll take a look!
 
New as in freshly installed with the Proxmox VE 9 ISO? In that case the environment is a bit unexpected for the tool, so such glitches might be present, but it's also not really required to be used as it's mainly for upgrades from PVE 8.
Still, can and should be improved, thanks for your report, we'll take a look!
No, 8.4 installed last week on a host that hasn't been used for anything yet.
 
Excellent news! :) Two quick questions:

1) The instructions don't explicitly state it - but do all VMs and LXCs have to be stopped before the in place upgrade? I have a stand alone PVE 8.4.8 with OPNSense VM allowing access to internet - if I shut that down, then I can't update that box from the internet ?!? :oops:

2) Can a working cluster of 5 be upgraded over a period of time? Mix and match VE 8.4.8 & VE 9 nodes in a cluster?
 
We are pleased to announce the first stable release of Proxmox Virtual Environment v9.0 - immediately available for download!

The new version is based on the great Debian 13 "Trixie" but we're using a newer Linux kernel 6.14.8-2 as stable default in Proxmox VE.
Beyond the core system updates, we've also refreshed many of our included technologies. You'll find updated versions of essential software like QEMU 10.0.2, LXC 6.0.4, ZFS 2.3.3, and Ceph Squid 19.2.3, all integrated seamlessly.

We're incredibly proud of the hard work that has gone into this release and can't wait for you to experience it.

Some of the exciting new features we've packed into Proxmox VE 9.0:
  • Snapshots as volume chains provide vendor-agnostic support for snapshots on any storage system that supports block storage. This includes iSCSI and Fibre Channel-attached SANs.
  • High-Availability (HA) rules for resource-to-node and resource-to-resource affinity
  • Fabrics for the Software-Defined Networking (SDN) stack
  • Modernized mobile web interface written in the rust programming language using the Yew web framework.
  • Comprehensive upgrade guide from 8 to 9
  • ZFS 2.3.3 with support for adding new devices to RAIDZ pools without downtime
  • and much more

Beyond these major additions, we've also implemented numerous performance enhancements and bug fixes to make your experience even smoother. For a full list of changes, check out our release notes.

Release notes
https://pve.proxmox.com/wiki/Roadmap

Press release
https://www.proxmox.com/en/news/press-releases

Download
https://www.proxmox.com/en/downloads
Alternate ISO download:
https://enterprise.proxmox.com/iso

Documentation
https://pve.proxmox.com/pve-docs

Community Forum
https://forum.proxmox.com

Bugtracker
https://bugzilla.proxmox.com

Source code
https://git.proxmox.com

There has been a lot of feedback from our community members and customers, and many of you reported issues, submitted patches, and were involved in testing - THANK YOU for your support!

FAQ
Q
: Can I upgrade latest Proxmox VE 8 to 9 with apt?
A: Yes, please follow the upgrade instructions on https://pve.proxmox.com/wiki/Upgrade_from_8_to_9

Q: Can I upgrade an 9.0 beta installation to the stable 9.0 via apt?
A: Yes, upgrading from beta to stable installation is possible via apt. We recommend switching to the pve-enterprise repository on upgrade for the most stable experience.

Q: How long will Proxmox VE 8.4 receive bug fixes and security support?
A: Proxmox VE 8.4 will receive security updates and critical bug fixes until August 2026. This support window provides an overlap of approximately one year after the release of Proxmox VE 9.0, giving users ample time to plan their upgrade to the new major version.
For more information on the support lifecycle of Proxmox VE releases, please visit:
https://pve.proxmox.com/pve-docs/chapter-pve-faq.html#faq-support-table

Q: Why is Proxmox VE 9.0 released ahead of the stable Debian 13 release?
A: Debian 13 is scheduled for its stable release this Saturday, August 9. Its core components have been stabilized since it entered the "hard freeze" phase on May 15. Following extensive integration testing and valuable feedback during the Proxmox VE 9.0 beta, we are confident in the stability of this release. Since our core packages are either maintained directly by the Proxmox team or are already locked by Debian's strict freeze policy, there is no technical reason to postpone our release.

Q: Can I install Proxmox VE 9.0 on top of Debian 13 "Trixie"?
A: Yes, see https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie

Q: Can I upgrade my Proxmox VE 8.4 cluster with Ceph Reef to v9.0?
A: This is a two-step process. First, you have to upgrade Ceph from Reef to Squid, and afterward you can upgrade Proxmox VE from 8.4 to 9.0. There are a lot of improvements and changes, so please follow the upgrade documentation exactly as described:
https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid
https://pve.proxmox.com/wiki/Upgrade_from_8_to_9

Q: Where can I get more information about feature updates?
A: Check the roadmap, forum, the mailing list, and/or subscribe to our newsletter.
Amazinh news...
Just ahead Debian 13 release...
Go go Proxmox...
 
A big congratulations is in place! Can't wait to update & enjoy!

Thanks to the awesome PVE team! :)
 
That's great news and hopefully I can take my hands on this soon. Have to wait for the linbit guys to provide trixie packages though...
 
No, 8.4 installed last week on a host that hasn't been used for anything yet.
So why not start with a fresh PVE 9 install from iso?
Unless you are doing it for testing purposes.

In all events - that error looks interesting & should be researched.
 
Excellent news! :) Two quick questions:

1) The instructions don't explicitly state it - but do all VMs and LXCs have to be stopped before the in place upgrade? I have a stand alone PVE 8.4.8 with OPNSense VM allowing accesuccessfullyss to internet - if I shut that down, then I can't update that box from the internet ?!? :oops:

2) Can a working cluster of 5 be upgraded over a period of time? Mix and match VE 8.4.8 & VE 9 nodes in a cluster?
1) i have a standalone 8.4 with pfsense as a vm for internet access, and the upgrade went through fine. i shut down all the VMs except pfsense and everything completed successfully.
 
  • Like
Reactions: gr3n
1) The instructions don't explicitly state it - but do all VMs and LXCs have to be stopped before the in place upgrade? I have a stand alone PVE 8.4.8 with OPNSense VM allowing access to internet - if I shut that down, then I can't update that box from the internet ?!? :oops:
This is to get in the cleanest state and avoid that the reboot takes longer than anticipated due to potnetially many machines needing to be stopped, and it's also a reminder that those with a cluster should leverage the (live) migration to reduce any impact for running VMs.
Besides that it normally is fine to keep virtual machines and containers running during the upgrade.
 
2) Can a working cluster of 5 be upgraded over a period of time? Mix and match VE 8.4.8 & VE 9 nodes in a cluster?
The clustering is in general compatible, but we only support migrating virtual guests from old to new, which might already limit running such a mixed cluster for a prolonged time, the other direction (migrating from a newer node to an older) is best effort only.
So while this might work, I'd not risk running such a setup for multiple weeks, if suddenly you need to make some infra or hardware changes you might have to finish the upgrade under pressure. That's why IMO always better to finish the upgrade as soon as possible, but still each cluster node one by one.
 
Last edited:
Excellent news! :) Two quick questions:

1) The instructions don't explicitly state it - but do all VMs and LXCs have to be stopped before the in place upgrade? I have a stand alone PVE 8.4.8 with OPNSense VM allowing access to internet - if I shut that down, then I can't update that box from the internet ?!? :oops:

2) Can a working cluster of 5 be upgraded over a period of time? Mix and match VE 8.4.8 & VE 9 nodes in a cluster?
If you need to upgrade your cluster without having access to the internet, you could look into setting up an instance of Proxmox Offline Mirror: https://pom.proxmox.com/ .

Caveat: I have no experience with this product yet.