Proxmox VE 8.3 released!

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
6,357
3,078
303
South Tyrol/Italy
shop.proxmox.com
We are excited to announce that our latest software version 8.3 for Proxmox Virtual Environment is now available for download. This release is based on Debian 12.8 "Bookworm" but uses a newer Linux kernel 6.8.12-4 and kernel 6.11 as opt-in, QEMU 9.0.2, LXC 6.0.0, and ZFS 2.2.6 (with compatibility patches for Kernel 6.11).

Proxmox VE 8.3 comes full of new features and highlights
  • Support for Ceph Reef and Ceph Squid
  • Tighter integration of the SDN stack with the firewall
  • New webhook notification target
  • New view type "Tag View" for the resource tree
  • New change detection modes for speeding up container backups to Proxmox Backup Server
  • More streamlined guest import from files in OVF and OVA
  • and much more
As always, we have included countless bugfixes and improvements on many places; see the release notes for all details.

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

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

Video tutorial
https://www.proxmox.com/en/training/video-tutorials/item/what-s-new-in-proxmox-ve-8-3

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 bugs, submitted patches and were involved in testing - THANK YOU for your support!

With this release we want to pay tribute to a special member of the community who unfortunately passed away too soon.
RIP tteck! tteck was a genuine community member and he helped a lot of users with his Proxmox VE Helper-Scripts. He will be missed. We want to express sincere condolences to his wife and family.

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

Q: Can I upgrade an 8.0 installation to the stable 8.3 via apt?
A: Yes, upgrading from is possible via apt and GUI.

Q: Can I install Proxmox VE 8.3 on top of Debian 12 "Bookworm"?
A: Yes, see https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm

Q: Can I upgrade from with Ceph Reef to Ceph Squid?
A: Yes, see https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid

Q: Can I upgrade my Proxmox VE 7.4 cluster with Ceph Pacific to Proxmox VE 8.3 and to Ceph Reef?
A: This is a three-step process. First, you have to upgrade Ceph from Pacific to Quincy, and afterwards you can then upgrade Proxmox VE from 7.4 to 8.3. As soon as you run Proxmox VE 8.3, you can upgrade Ceph to Reef. There are a lot of improvements and changes, so please follow exactly the upgrade documentation:
https://pve.proxmox.com/wiki/Ceph_Pacific_to_Quincy
https://pve.proxmox.com/wiki/Upgrade_from_7_to_8
https://pve.proxmox.com/wiki/Ceph_Quincy_to_Reef

Q: Where can I get more information about feature updates?
A: Check the roadmap, forum, the mailing list, and/or subscribe to our newsletter.
 
Thanks! Already updating, keep up the great work! Thanks for the pre-christmas present!

1732192500180.png
 
This is quite a good way to install, the proxmox feature and not be force to get a defective kernel directly. Of course old hardware or server grade is a different story.. esxi do run with an approved list and proxmox do not. Great version so far. Ova import run perfect !
We will look to migrate from v8.0 with fresh install, then never update. A server is not a phone.
 
MULTI
DATACENTER
MANAGEMENT
CONSOLE

We need a replacement for vSphere, touching every device one by one is a major time drain.
 
MULTI
DATACENTER
MANAGEMENT
CONSOLE

We need a replacement for vSphere, touching every device one by one is a major time drain.
Stay on topic and until we release something like that, which will not just be a PVE feature anyway, use automation and our REST API and you will have much less work than any multi-something can give you.
 
Are releases pushed to enterprise subscription repositories first, then to no-subscription ones later?
No, it's vice versa. A lot of the new updates were already available on the no-subscription since a few days/weeks, and got moved only today to the enterprise repository, i.e. after some further polishing and shaking out some (smaller) bugs.
 
Last edited:
Even though I can upload an OVA to my local repo, I can't deploy from it. When I upload to my NFS share, I can. Will local OVA support be supported?


1732205057363.png
 
Even though I can upload an OVA to my local repo, I can't deploy from it. When I upload to my NFS share, I can. Will local OVA support be supported?
You either need to enable the "images" content type for the "local" storage (Datacenter -> Storages -> select "local" -> Edit) or explicitly select a storage that is configured to allow the "images" content type as "working directory".

The reason here is that we need a "real" PVE storage for an intermediate extraction of the OVA image so that we can actually parse configs and ensure everything can work as PVE expects, and doing so requires the "images" content type to be available.
 
  • Like
Reactions: Johannes S
Hi! New Proxmox user here (and LOVING IT). In my home environment I just have one Proxmox server that has a few vms and containers on it. I ran the update and looks like it took me from 8.2 to 8.3.

Everything seems fine. Nothing skipped a beat. Do I have to restart? It didn't say so. I think it restarted the web UI because my console came disconnected right at the tail end of it, but I reconnected and checked for updates again and it says I'm all up to date. So that's it? It's a simple non-event?

This is a user who's used vmware professionally for 14+ years and used to a maintenance mode > reboot.
 
Is Proxmox Backup server compatible with the current version or should we wait before rolling out the Proxmox VE update?
Yes, we do not break compatibility within a major release and try hard to stay compatible as long as possible.
 
You either need to enable the "images" content type for the "local" storage (Datacenter -> Storages -> select "local" -> Edit) or explicitly select a storage that is configured to allow the "images" content type as "working directory".

The reason here is that we need a "real" PVE storage for an intermediate extraction of the OVA image so that we can actually parse configs and ensure everything can work as PVE expects, and doing so requires the "images" content type to be available.
Great Job guys on the UI interface for importing!

is this just using the qm disk import command once its at the step of copying the data into the new virtual disk media? if so, does this technically also work with VHD's and you just don't have it listed?
 
Great Job guys on the UI interface for importing!

is this just using the qm disk import command once its at the step of copying the data into the new virtual disk media? if so, does this technically also work with VHD's and you just don't have it listed?
I have confirmed that the UI menu does not allow you to finish uploading it as a VHDX as it complains about the wrong file extension. I will have play around with just giving the VHDX an ova/ovf extension on upload and see what happens.

For refrence, normally what I do when I go and import using the CLI; I create the VM first then target the VM's main disk with the qm import command with the VHDX as the source. I've successfully done this with every attempt I've made and have multiple successfully VM's in production like this.
 
I just updatet to 8.3 and only got errors. It now doesn't startup (journalctl -xeu pvestatd.service)

Code:
Nov 21 19:37:24 proxian.lan.martijnmeijer.net systemd[1]: Starting pvestatd.service - PVE Status Daemon...
░░ Subject: A start job for unit pvestatd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pvestatd.service has begun execution.
░░
░░ The job identifier is 171.
Nov 21 19:37:24 proxian.lan.martijnmeijer.net pvestatd[3317]: ipcc_send_rec[1] failed: Connection refused
Nov 21 19:37:24 proxian.lan.martijnmeijer.net pvestatd[3317]: ipcc_send_rec[2] failed: Connection refused
Nov 21 19:37:24 proxian.lan.martijnmeijer.net pvestatd[3317]: ipcc_send_rec[3] failed: Connection refused
Nov 21 19:37:24 proxian.lan.martijnmeijer.net pvestatd[3317]: Unable to load access control list: Connection refused
Nov 21 19:37:24 proxian.lan.martijnmeijer.net pvestatd[3317]: ipcc_send_rec[1] failed: Connection refused
Nov 21 19:37:24 proxian.lan.martijnmeijer.net pvestatd[3317]: ipcc_send_rec[2] failed: Connection refused
Nov 21 19:37:24 proxian.lan.martijnmeijer.net pvestatd[3317]: ipcc_send_rec[3] failed: Connection refused
Nov 21 19:37:24 proxian.lan.martijnmeijer.net systemd[1]: pvestatd.service: Control process exited, code=exited, status=111/n/a

Looks like https://forum.proxmox.com/threads/after-update-job-for-pvestatd-service-failed.91089/

Solved., somehow the hostname kept being reset by in the /etc/hosts file to the hostname of one of the VM's
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!