From: Martin Maurer <martin@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
pve-user@pve.proxmox.com
Subject: [PVE-User] Proxmox VE 7.1 released!
Date: Wed, 17 Nov 2021 11:32:12 +0100 [thread overview]
Message-ID: <82d88ac5-7548-8df4-9499-ce510d07dad6@proxmox.com> (raw)
Hi all,
we're excited to announce the release of Proxmox Virtual Environment 7.1. It's based on Debian 11.1 "Bullseye" but using a newer Linux kernel 5.13, QEMU 6.1, LXC 4.0, Ceph 16.2.6, and OpenZFS 2.1. and countless enhancements and bugfixes.
Proxmox Virtual Environment brings several new functionalities and many improvements for management tasks in the web interface: support for Windows 11 including TPM, enhanced creation wizard for VM/container, ability to set backup retention policies per backup job in the GUI, and a new scheduler daemon supporting more flexible schedules..
Here is a selection of the highlights
- Debian 11.1 "Bullseye", but using a newer Linux kernel 5.13
- LXC 4.0, Ceph 16.2.6, QEMU 6.1, and OpenZFS 2.1
- VM wizard with defaults for Windows 11 (q35, OVMF, TPM)
- New backup scheduler daemon for flexible scheduling options
- Backup retention
- Protection flag for backups
- Two-factor Authentication: WebAuthn, recovery keys, multiple factors for a single account
- New container templates: Fedora, Ubuntu, Alma Linux, Rocky Linux
- and many more enhancements, bugfixes, etc.
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.1
Press release
https://www.proxmox.com/en/news/press-releases/proxmox-virtual-environment-7-1-released
Video tutorial
https://www.proxmox.com/en/training/video-tutorials/item/what-s-new-in-proxmox-ve-7-1
Download
https://www.proxmox.com/en/downloads
Alternate ISO download:
http://download.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 to 7.1 via GUI?
A: Yes.
Q: Can I upgrade Proxmox VE 6.4 to 7.1 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.1 on top of Debian 11.1 "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.1 with Ceph Octopus/Pacific?
A: This is a two step process. First, you have to upgrade Proxmox VE from 6.4 to 7.1, 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 roadmap, forum, the mailing list, and/or subscribe to our newsletter.
--
Best Regards,
Martin Maurer
martin@proxmox.com
https://www.proxmox.com
reply other threads:[~2021-11-17 10:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=82d88ac5-7548-8df4-9499-ce510d07dad6@proxmox.com \
--to=martin@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=pve-user@pve.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