Proxmox VE 6


What’s new in Proxmox VE 6.1
Container: Proxmox VE 6.1 brings new features for containers such as pending changes. It is now possible to make changes to running containers and they will be applied after the following reboot. A reboot of a running container is either possible via the GUI, the API, or the command line interface. Hot plugging of mount points are now enabled by using the new mount API available with Linux Kernel 5.3.
Ease of management and improved access security: The Proxmox design team has added countless new features to the web-based user interface.
If the package ifupdown2 of the Debian network interface manager is installed, it’s now possible to change the network configuration and reload it in the Proxmox web interface without a reboot.
Added configuration options including settings for Universal 2nd Factor (U2F) or editing the cluster-wide bandwidth limit for the traffic types migration, backup/restore, cloning, disk-move are available.
Improvements to the two-factor authentication allowing to use a hardware-based TOTP key.
Mobile interface: In the mobile interface a login for TOTP-based two-factor authentication enabled user accounts has been implemented.
The scale mode of noVNC can be changed in “My Settings”.
A new “Run now” button for cluster-wide backup jobs has been implemented.
SPICE improvements: For a seamless remote access to virtual machines, a couple of SPICE enhancements are now available in the GUI. With Proxmox VE version 6.1 audio devices can be added without the need to edit the configuration file. Also video streaming can be enabled, and sharing folders between the SPICE client and a VM is possible (although still experimental). The SPICE USB device now supports USB3 (if using Qemu 4.1 or greater).
Backup/Restore: VMs with IOThreads enabled can be backed up with Proxmox VE 6.1. Additionally, administrators can run scheduled backup jobs manually from the Datacenter in the GUI.
Improvements to the HA stack:
New ‘migrate’ shutdown policy: If the new migrate option is enabled, running services are migrated to another node on shutdown. As soon as the node comes back and the services were not manually moved to another node in the meantime, the services will move back.
New ‘crm-command stop’: Shuts down a VM/container with the specified timeout and performs a hard stop if the timeout is 0. A VM or container stop command will be redirected to this new crm-command.

Read more course:  The Advanced Web Developer Course

Proxmox VE 6, Free Tutorials Download

Download Proxmox VE 6 Free Tutorials Direct Links

Go to Download Tutorials Page

Password :


Related Courses

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.