Proxmox VE 8.2 veröffentlicht

Proxmox VE Logo

Proxmox VE Logo

Die Virtualisierungslösung Proxmox VE wurde vor wenigen Tagen aktualisiert und liegt nun in Version 8.2 vor. Nach den Änderungen bei VMware in den letzten Wochen ist Proxmox VE zu einer echten Alternative geworden. Die Proxmox Servers Solution GmbH mit Sitz in Österreich hat hier reagiert und bietet mit der neuen Version von Proxmox VE 8.2, vorerst für alle ESXi Administratoren, einen Import Wizard. Dieser ermöglicht die Migration von VMware ESXi Gästen zu Proxmox VE.

Highlights Proxmox VE 8.2

Proxmox VE 8.2 Release Notes


Changelog Overview

Enhancements in the web interface (GUI)

Virtual machines (KVM/QEMU)

Containers (LXC)

General improvements for virtual guests

Improved management for Proxmox VE clusters




Access control

Firewall & Software-Defined Networking

Improved management of Proxmox VE nodes

Installation ISO

Notable changes

Known Issues & Breaking Changes

Kernel 6.8

The Proxmox VE 8.2 releases will install and use the 6.8 Linux kernel by default, a major kernel change can have a few, hardware specific, side effects.

You can avoid installing the 6.8 kernel by pinning the proxmox-default-kernel package version before the upgrade. The last version to depend on kernel 6.5 is 1.0.1.

To pin the package to that version, create a file in /etc/apt/preferences.d/proxmox-default-kernel with the following content. This will keep proxmox-default-kernel on the old version until that file is deleted, and a new upgrade is initiated:

Package: proxmox-default-kernel
Pin: version 1.0.1
Pin-Priority: 1000

Kernel: Change in Network Interface Names

Upgrading kernels always carries the risk of network interface names changing, which can lead to invalid network configurations after a reboot. In this case, you must either update the network configuration to reflect the name changes, or pin the network interface to its name beforehand.

See the reference documentation on how to pin the interface names based on MAC Addresses.

Currently, the following models are known to be affected at higher rates:

Kernel: DKMS

Since the default kernel changes to 6.8, it may happen that installed DKMS modules will not build anymore. For instance, as of April 2024 this is the case for the latest NVIDIA GRID driver 17.1.

Aside from simply removing and not using those modules, one possible workaround is to pin the proxmox-default-kernel package to an older version before the upgrade. The last version to depend on kernel 6.5 is 1.0.1.

Kernel: Split Lock Detection Slowing Down VMs

If the host CPU supports split lock detection and a VM is performing misaligned memory accesses, the host kernel might artificially slow down the VM as of kernel version 5.19 or later.

There’s now a wiki article on split lock detection with more information.

Old Ceph Crash Reports

The Ceph crash service monitors other Ceph daemons for crashes and reports them as a health warning. This service did not work properly with Proxmox VE’s ceph server integration due to some internal ceph restructuring. This has been fixed with the ceph packages uploaded with the Proxmox VE 8.2 release, but this also means that it will now catch up on reporting older crashes, even if they happened a few weeks or months ago.

If you see a Ceph health warning due to services being reported as crashed, please also check the date of the crash to avoid mistaking it for a recent crash caused by the upgrade.

Press Release unter: https://www.proxmox.com/en/about/press-releases/proxmox-virtual-environment-8-2

Die mobile Version verlassen