From: Martin Maurer <martin@proxmox.com>
To: pve-devel@lists.proxmox.com, pve-user@lists.proxmox.com
Subject: [PVE-User] Proxmox VE 7.2 released!
Date: Wed, 4 May 2022 12:27:27 +0200 [thread overview]
Message-ID: <e32512e9-ebbb-ceea-d2b8-0662111057e3@proxmox.com> (raw)
Hi all,
we're excited to announce the release of Proxmox Virtual Environment
7.2. It's based on Debian 11.3 "Bullseye" but using a newer Linux kernel
5.15.30, QEMU 6.2, LXC 4, Ceph 16.2.7, and OpenZFS 2.1.4 and countless
enhancements and bugfixes.
Here is a selection of the highlights
- Support for the accelerated virtio-gl (VirGL) display driver
- Notes templates for backup jobs (e.g. add the name of your VMs and CTs
to the backup notes)
- Ceph erasure code support
- Updated existing and new LXC container templates (New: Ubuntu 22.04,
Devuan 4.0, Alpine 3.15)
- ISO: Updated memtest86+ to the completely rewritten 6.0b version,
adding support for UEFI and modern memory like DDR5
- and many more GUI enhancements
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#Proxmox_VE_7.2
Press release
https://www.proxmox.com/en/news/press-releases/proxmox-virtual-environment-7-2-available
Video tutorial
https://www.proxmox.com/en/training/video-tutorials/item/what-s-new-in-proxmox-ve-7-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 shout out a big THANK YOU to our active community for all
your intensive feedback, testing, bug reporting and patch submitting!
FAQ
Q: Can I upgrade Proxmox VE 7.0 or 7.1 to 7.2 via GUI?
A: Yes.
Q: Can I upgrade Proxmox VE 6.4 to 7.2 with apt?
A: Yes, please follow the upgrade instructions on
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0
Q: Can I install Proxmox VE 7.2 on top of Debian 11.x "Bullseye"?
A: Yes, see
https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye
Q: Can I upgrade my Proxmox VE 6.4 cluster with Ceph Octopus to 7.2 with
Ceph Octopus/Pacific?
A: This is a two step process. First, you have to upgrade Proxmox VE
from 6.4 to 7.2, and afterwards upgrade Ceph from Octopus to Pacific.
There are a lot of improvements and changes, so please follow exactly
the upgrade documentation:
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0
https://pve.proxmox.com/wiki/Ceph_Octopus_to_Pacific
Q: Where can I get more information about feature updates?
A: Check the https://pve.proxmox.com/wiki/Roadmap,
https://forum.proxmox.com/, the https://lists.proxmox.com/, and/or
subscribe to our https://www.proxmox.com/en/news.
--
Best Regards,
Martin Maurer
martin@proxmox.com
https://www.proxmox.com
next reply other threads:[~2022-05-04 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 10:27 Martin Maurer [this message]
2022-05-04 12:10 ` [PVE-User] Proxmox VE 7.2 - Problem of understanding 'bridge-disable-mac-learning' Martin Dziobek
2022-05-04 13:39 ` Stoiko Ivanov
2022-05-05 13:24 ` DERUMIER, Alexandre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e32512e9-ebbb-ceea-d2b8-0662111057e3@proxmox.com \
--to=martin@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox