Proxmox VE 8.2 released!

martin

martin

Proxmox Staff Member
Staff member
Apr 28, 2005
754
1,723
223
We are excited to announce that our latest software version 8.2 for Proxmox Virtual Environment is now available for download. This release is based on Debian 12.5 "Bookworm" but uses a newer Linux kernel 6.8, QEMU 8.1, LXC 6.0, Ceph 18.2 and ZFS 2.2.

We have an import wizard to migrate VMware ESXi guests to Proxmox VE. The integrated VM importer is presented as storage plugin for native integration into the API and web-based user interface. You can use this to import the VM as a whole, with most of the original configuration settings mapped to Proxmox VE's configuration model.

With the new ‘proxmox-auto-install-assistant’ tool you can fully automate the setup process on bare-metal, rapidly deploying Proxmox VE hosts without the need for manual access to the systems.

Proxmox VE 8.2 comes full of new features and highlights
  • Debian 12.5 (“Bookworm”), but uses a newer Linux kernel 6.8 as stable default
  • Latest versions of QEMU 8.1, LXC 6.0, Ceph 18.2
  • Import wizard to migrate VMware ESXi guests to Proxmox VE
  • A new tool for automated installation from the ISO to bare-metal servers
  • Backup fleecing feature implementation: decouple slower backup storage from the VM performance
  • Firewall modernization with nftables (tech preview)
  • Countless GUI and API improvements.
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/services/videos/proxmox-virtual-environment/whats-new-in-proxmox-ve-8-2

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

We want to thank everyone who has contributed to this release, whether it's through code contributions, bug reports, or simply using and providing feedback on the software. As always, we welcome any feedback or bug reports you may have. Thanks again for your support, and happy virtualization!

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.2 via apt?
A: Yes, upgrading from is possible via apt and GUI.

Q: Can I install Proxmox VE 8.2 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 my Proxmox VE 7.4 cluster with Ceph Pacific to Proxmox VE 8.2 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.2. As soon as you run Proxmox VE 8.2, 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.

__________________
Best regards,

Martin Maurer
Proxmox VE project leader
 
  • Like
Reactions: SBMe, Phyrene, MON@H and 28 others
Usually it's lot of bug with main version and we wait for x.x.1 and so. But as currently over the realese note.. it is just minor fix and more for the esxi public who were using esxi8 instead of remaining on v7. Anyhow, currently installing to see if assignation of multiple ntwrk card do work better.
-as always a server is not a phone, no reason to do any update if all work.
 
Docop2 said:
-as always a server is not a phone, no reason to do any update if all work.
Click to expand...
Except you don't get (security) fixes then. Especially kernel updates are always important for any kind of networked device.
 
  • Like
Reactions: IsThisThingOn, MON@H, Andre W. and 5 others
Loving the more 'human' voice over in the latest videos compared to the obvious robot voice ;) I was trying to tell if it was an AI voiceover or a real person. Anyway, hosts have been updated to the latest version. Keep up the great work guys!
 
  • Like
Reactions: jsterr and El Tebe
Firebat said:
I have problems with the new 6.8 kernel. Is it possible that the interface names change with an Intel X710 card? With 6.5 my interface was called enp99s0f0, with the 6.8 kernel the same interface is now called enp99s0f0np0. This tears up the entire network configuration...
Click to expand...
You can pin the names to be consistent over udev changes that might come with debian updates.
 
  • Like
Reactions: Tobias.F and Der Harry
Yes, but this just happened after kernel change and wasn't an issue from 6.2 to 6.5 in the past. I would expect this to be enabled by default or at least with a warning or information in the release notes... Just tried to update a second host and again only the X710 interfaces are affected.

before.pngafter.png
 
  • Like
Reactions: andli86 and Tobias.F
Update hanging at update-grub....
rebooted.. now some vms dont start and web ui hangs.
What i tried so far:
grub-probe --device /dev/mapper/pve-root --target=fs_uuid

all partitions are ext4.
 
Hello! Congratulations on the release!

What are the implications of running the latest 6.5.13 kernel with Proxmox 8.2? I'm experimenting with Intel iGPU SR-IOV support, and that still requires the latest 6.5.13 release.

Is booting with 6.5 going to break any of the new features?

Edit: I noticed this in the release notes: "When editing ZFS storages, display 16k as the blocksize placeholder to reflect the current ZFS defaults."
However, after upgrading and restarting, I tried to add a new ZFS pool an saw this:
1713971574057.png

Thanks!
 
Last edited:
I get this error while upgrading:

Code: 
Building module:
Cleaning build area...
make -j32 KERNELRELEASE=6.8.4-2-pve -C src/drbd KDIR=/lib/modules/6.8.4-2-pve/build.......(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.8.4-2-pve (x86_64)
Consult /var/lib/dkms/drbd/9.2.8-2/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.8.4-2-pve failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.8.4-2-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.8.4-2-pve-signed (--configure):
 installed proxmox-kernel-6.8.4-2-pve-signed package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-6.8:
 proxmox-kernel-6.8 depends on proxmox-kernel-6.8.4-2-pve-signed | proxmox-kernel-6.8.4-2-pve; however:
  Package proxmox-kernel-6.8.4-2-pve-signed is not configured yet.
  Package proxmox-kernel-6.8.4-2-pve is not installed.
  Package proxmox-kernel-6.8.4-2-pve-signed which provides proxmox-kernel-6.8.4-2-pve is not configured yet.

dpkg: error processing package proxmox-kernel-6.8 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-default-kernel:
 proxmox-default-kernel depends on proxmox-kernel-6.8; however:
  Package proxmox-kernel-6.8 is not configured yet.

dpkg: error processing package proxmox-default-kernel (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on proxmox-default-kernel; however:
  Package proxmox-default-kernel is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 proxmox-kernel-6.8.4-2-pve-signed
 proxmox-kernel-6.8
 proxmox-default-kernel
 proxmox-ve

I found no solution to successfully finish the update.
Any ideas how to continue the update?
 
SInisterPisces said:
Edit: I noticed this in the release notes: "When editing ZFS storages, display 16k as the blocksize placeholder to reflect the current ZFS defaults."
However, after upgrading and restarting, I tried to add a new ZFS pool an saw this:
View attachment 66885

Thanks!
Click to expand...

Did you reload your web gui after rebooting?
 
  • Like
Reactions: Feni, gseeley, SInisterPisces and 1 other person
I know that you've published a bug tracker portal for requesting new features by the users, but referring to the newest "Import wizard to migrate VMware ESXi guests to Proxmox VE" innovation and taking the opportunity:

It also would be nice to get the "import OVA image wizard" option.

:)
 
  • Like
Reactions: VictorSTS, Andre W. and pschneider1968
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back