Proxmox VE 9.0 BETA released!

t.lamprecht

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
6,596
4,037
303
South Tyrol/Italy
shop.proxmox.com
We are pleased to announce the first beta release of Proxmox Virtual Environment 9.0! The 9.x family is based on the great Debian 13 "Trixie" and comes with a 6.14.8-1 kernel, QEMU 10.0.2, LXC 6.0.4, OpenZFS 2.3.3.

Note: The current release of Proxmox Virtual Environment 9.0 is a beta version. If you test or upgrade, make sure to first create backups of your data. We recommend Proxmox Backup Server to do so.

Here are some of the highlights of the Proxmox VE 9.0 beta version
  • Ceph Squid 19.2 is the new default and comes with continued support
  • SDN Fabrics for complex routed networks, enabling advanced use cases like two-layer spine-leaf architectures or a full-mesh Ceph cluster.
  • Snapshots for thick-provisioned LVM shared storage, e.g., for setups connected over iSCSI or Fibre Channel to a SAN.
  • ZFS 2.3 with RAID-Z expansion.
  • Countless GUI and API improvements.
  • and much more...
Release notes
https://pve.proxmox.com/wiki/Roadmap

Download
https://enterprise.proxmox.com/iso

Community Forum
https://forum.proxmox.com

Bugtracker
https://bugzilla.proxmox.com

Source code
https://git.proxmox.com

FAQ
Q: Is the Proxmox VE 9.0 beta safe to use?
A: You should never upgrade critical production systems to the beta, it's not a stable release and it does not get security support.
While we try hard to avoid severe bugs, some instability is expected.

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

Q: Can I upgrade a 9.0 beta installation to the stable 9.0, once released, via apt?
A: Yes, upgrading from beta to stable installation will be possible via apt.

Q: Which apt repository can I use for Proxmox VE 9.0 beta?
A: You can use the pve-test repository:

Code: 
deb http://download.proxmox.com/debian/pve trixie pve-test

Q: Will the beta receive updates and new features?
A: Yes, the beta will continuously receive updates including the latest fixes and features.

Q: Can I install Proxmox VE 9.0 beta 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 9.0 beta?
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 exactly the upgrade documentation:
https://pve.proxmox.com/wiki/Upgrade_from_8_to_9
https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid

Q: When do you expect the stable Proxmox VE 9.0 release?
A: The final Proxmox VE 9.0 will be available as soon as all Proxmox VE 9.0 release critical bugs are fixed, and new features are deemed stable.

Q: Where can I get more information about feature updates?
A: Check the roadmap, forum, the mailing list, and/or subscribe to our newsletter.

You are welcome to test your hardware and your upgrade path, and we are looking forward to your feedback, bug reports, or ideas. Thank you for getting involved!
 
  • Like
Reactions: fireon, the_Uli, christophe and 16 others
mikeyo said:
Anyone else have issues downloading ISO releases from https://enterprise.proxmox.com/iso/ ? It always stalls right at the end and I end up having to torrent the file, really frustrating.
Click to expand...

We do not have a torrent file published as we normally only do that for stable releases, but you can use the following magnet link:

Code: 
magnet:?xt=urn:btih:15722cc3e0da53c180be9c99d86717a665e073e0&dn=proxmox-ve%5F9.0-BETA-1.iso&tr=http%3A%2F%2Ftorrent.cdn.proxmox.com%3A6969%2Fannounce
 
  • Like
Reactions: Johannes S and mikeyo
t.lamprecht said:
We do not have a torrent file published as we normally only do that for stable releases, but you can use the following magnet link:

Code: 
magnet:?xt=urn:btih:15722cc3e0da53c180be9c99d86717a665e073e0&dn=proxmox-ve%5F9.0-BETA-1.iso&tr=http%3A%2F%2Ftorrent.cdn.proxmox.com%3A6969%2Fannounce
Click to expand...
Thanks!
 
I think I followed the update in place guide but ended up with a duplicate modernize-sources entry for
Code: 
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-test
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
Which is the preferred location?
  • /etc/apt/sources.list.d/proxmox.sources
  • /etc/apt/sources.list.d/pve-test-for-beta.sources
 
readyspace said:
What are the technical considerations and limitations of implementing SDN Fabrics for two-layer spine-leaf topologies in Proxmox VE 9.0?
Click to expand...
Would be nice to have beta documentation too :)

Find odd the election of OSPF, when the most usual setup in the data center is BGP based and EVPN is already heavily used in PVE SDN.
 
uzumo said:
the following URL, which worked on pve8 with pci pass-through for Alderlake igpu, did not work on pve9
Click to expand...
For me in in pve9 handles Alder Lake i5-1235U pass through of iGPU with local video and sound output with default settings for Ubuntu 25.10 VM. In contrast for me I could not get pve8 to pass through sound (Codec not found for Intel Alderlake PCH-P High definition Audio Controller)

However
GUI -> VM Summary -> now shows
IPs: Requires 'VM.Monitor' Privileges
for all my VMs that reported OK in pve8
 
Last edited:
  • Like
Reactions: Johannes S
The wiki-post says:
Make sure that apt picks it up correctly with apt policy. Then remove the previous Proxmox VE 8 no-subscription repository from either the /etc/apt/sources.list, /etc/apt/sources-list.d/pve-install-repo.list or any other .list file you may have added it to. You can use apt policy again to make sure the old repository is not being used anymore.
Click to expand...
How to do that? running apt policy seems not to be the full command? Might be useful adding an example on howto check.

Also apt update brings up the following, might be related to check seeing if the new repo-format is used or not. My sources.list still contains pvetest instead of pve-test. Or my old pve-installation has already used pvetest which now is called pve-test.

Code: 
W: Skipping acquire of configured file 'pvetest/binary-amd64/Packages' as repository 'http://download.proxmox.com/debian/pve trixie InRelease' doesn't have the component 'pvetest' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'pvetest/i18n/Translation-en' as repository 'http://download.proxmox.com/debian/pve trixie InRelease' doesn't have the component 'pvetest' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'pvetest/i18n/Translation-en_US' as repository 'http://download.proxmox.com/debian/pve trixie InRelease' doesn't have the component 'pvetest' (component misspelt in sources.list?)
root@pveneo:/etc/apt#

Edit: Seems like you need to just do a apt update before checking via apt policy. Might be useful to add this to the wiki. As apt policy just returns way less if you do not do a apt update before.

Code: 
root@pveneo:/etc/apt/sources.list.d# apt policy
Package files:
 100 /var/lib/dpkg/status
     release a=now
Pinned packages:
 
Last edited:
After upgrading to the beta, I get an error on all my vms regarding cloudinit + also for my ct, that are on a lvm-thin pool. all vms and ct cant start:

Code: 
TASK ERROR: activating LV 'pve/vm-103-cloudinit' failed:   Check of pool pve/data failed (status:64). Manual repair required!
TASK ERROR: activating LV 'pve/data' failed:   Check of pool pve/data failed (status:64). Manual repair required!
TASK ERROR: activating LV 'pve/vm-103-cloudinit' failed:   Check of pool pve/data failed (status:64). Manual repair required!

Info: I did run the migration script before, although Im on a local lvm-pool.
Can you add an information on howto fix this? (Although it seems like a bug and should not happen?)

Code: 
root@pveneo:~# lvs
  LV                VG  Attr       LSize    Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  base-104-disk-0   pve Vri---tz-k    4.00m data                                           
  base-104-disk-1   pve Vri---tz-k   32.00g data                                           
  base-104-disk-2   pve Vri---tz-k   32.00g data                                           
  base-9001-disk-0  pve Vri---tz-k   12.00g data                                           
  data              pve twi---tz-- <319.61g                                               
  root              pve -wi-ao----   96.00g                                               
  swap              pve -wi-ao----    8.00g                                               
  vm-101-cloudinit  pve Vwi---tz--    4.00m data                                           
  vm-101-disk-0     pve Vwi---tz--  125.00g data                                           
  vm-102-cloudinit  pve Vwi---tz--    4.00m data                                           
  vm-102-disk-0     pve Vwi---tz--   60.00g data                                           
  vm-103-cloudinit  pve Vwi---tz--    4.00m data                                           
  vm-103-disk-0     pve Vwi---tz--   12.00g data                                           
  vm-105-disk-0     pve Vwi---tz--   62.00g data                                           
  vm-111-cloudinit  pve Vwi---tz--    4.00m data                                           
  vm-111-disk-0     pve Vwi---tz--   60.00g data                                           
  vm-9001-cloudinit pve Vwi---tz--    4.00m data                                           
root@pveneo:~# pvs
  PV         VG  Fmt  Attr PSize   PFree
  /dev/sda3  pve lvm2 a--  446.12g 16.00g
root@pveneo:~# vgs
  VG  #PV #LV #SN Attr   VSize   VFree
  pve   1  17   0 wz--n- 446.12g 16.00g

Edit: Fix via thin_check_options = [ "-q", "--skip-mappings" ] see link below.

I fixed this with https://forum.proxmox.com/threads/l...rnel-update-on-pve-7.97406/page-2#post-430860 seems like its related to having lvm-thin pool overprovisioned.
 
Last edited:
  • Like
Reactions: waltar and Johannes S
patch said:
/etc/apt/sources.list.d/pve-test-for-beta.sources
Click to expand...
This is just the one for the beta and gets auto added, but actially will matter soley for new installations. We will look into improving the heuristic that adds it, thanks for the report
 
  • Like
Reactions: Johannes S
t.lamprecht said:
This is just the one for the beta and gets auto added, but actially will matter soley for new installations. We will look into improving the heuristic that adds it, thanks for the report
Click to expand...
Does that mean that it can be safely removed after a succesful upgrade?
 
Twilek said:
Does that mean that it can be safely removed after a succesful upgrade?
Click to expand...
The duplicate one yes, just ensure you got at least one enabled left - you can check the node's Repository panel on the web UI to ensure that, there you can also add back a repo back at any time.
 
  • Like
Reactions: Twilek
You must log in or register to reply here.
Top Bottom