Published release of Proxmox Virtual Environment 9.1, a specialized Linux distribution based on Debian GNU/Linux, aimed at deployment and maintenance of virtual servers using LXC and KVM, and can act as a replacement for products such as VMware vSphere, Microsoft Hyper-V and Citrix Hypervisor. The size of the installation iso image is 1.7 GB.
Proxmox VE provides the means to deploy a complete system of industrial-grade virtual servers managed via a web interface, designed to manage hundreds or even thousands of virtual machines. The distribution has built-in tools for organizing backups of virtual environments and clustering support available out of the box, including the ability to migrate virtual environments from one node to another without stopping work. Among the features of the web interface: support for a secure VNC console; role-based access control to all available objects (VM, storage, nodes, etc.); support for various authentication mechanisms (MS ADS, LDAP, Linux PAM, Proxmox VE authentication).
In new release:
- Implemented synchronization with the Debian 13.2 package database. The Linux kernel has been updated to release 6.17. New releases of QEMU 10.1.2, LXC 6.0.5, ZFS 2.3.4 are involved. Support for creating storages based on Ceph 19.2.3 (Squid) is available.
- Added the ability to create LXC containers from images in OCI (Open Container Initiative) format, downloaded manually or from repositories. It supports the creation of container templates from OCI, containers with a complete system environment, and containers for running individual applications.
- For containers that require attaching a virtual TPM (Trusted Platform Module), the ability to save the vTPM state in the qcow2 format has been implemented. This feature allows you to create snapshots of virtual machines with vTPM, for example, those used to run guest systems with new versions of Windows, using file storage based on NFS and CIFS.
- Tools are provided for flexible management of nested virtualization in guest systems. Added a new vCPU flag “nested-virt”, which allows you to enable nested virtualization on top of a vCPU type that fully or partially matches the parameters (manufacturer and generation) of the host CPU. Examples of the use of nested virtualization include the launch of nested hypervisors and the use of virtualization-based Windows security mechanisms in guest systems.