Loading Now

Proxmox VE 9.0: The Ultimate Virtualization Beast is Here

Proxmox VE 9.0: The Ultimate Virtualization Beast is Here

Attention sysadmins, virtualization enthusiasts, and infrastructure specialists! The moment we’ve eagerly anticipated has finally arrived! Proxmox VE 9.0 is officially out, bringing the kind of power that rivals a fully equipped blade server. This release, based on the robust Debian 13 “Trixie” and equipped with a cutting-edge Linux Kernel 6.14, is poised to revolutionise your virtualization tasks like never before.

New Features and Improvements

System Overview

Base Operating System Debian 13 “Trixie”
Kernel Version Linux 6.14.8
Hypervisor QEMU 10.0.2
Container Runtime LXC 6.0.4
Storage System OpenZFS 2.3.3
Distributed Storage Ceph Squid 19.2.3

Highlighted Enhancements

Volume Chain Snapshots

Take advantage of storage-agnostic snapshot capabilities for any storage solution. Be it iSCSI, Fibre Channel, or even your vintage NAS, we’ll manage snapshots with ease, creating volume chains independent of vendor-specific implementations.

Sophisticated HA Management

Forget about the basic HA groups of the past. The enhanced HA rules allow for precise control over resource affinity, ensuring your essential VMs are placed exactly where you intend, with detailed specifications for placement and failover strategies.

Upgraded SDN Features

Software-Defined Networking has undergone a significant transformation. Enjoy simplified configurations for complex networks—because nobody wants the hassle of manual VLAN setups. The updated SDN features introduce layers of abstraction to streamline intricate network architectures.

Revamped Mobile User Interface

Managing your hyperconverged infrastructure via your mobile device has never been easier. The touch-optimised interface has been entirely redesigned for swifter navigation, allowing you to oversee your cluster while on the go.

Network Interface Pinning Utility

The new proxmox-network-interface-pinning tool ensures consistent NIC naming during upgrades. Your eth0 will stay eth0, maintaining stability through updates, resolving one of the most common frustrations during kernel upgrades.

RAIDZ Pool Expansion

At last! You can now enlarge your RAIDZ pools without needing to start anew. Experience ZFS flexibility combined with enterprise-level scalability—a much-requested feature that aligns ZFS on Linux with Solaris ZFS capabilities.

Improvements in Performance & Hardware

Kernel 6.14: A Performance Boost

  • PCIe 5.0 Compatibility – Your ultra-fast NVMe drives will benefit from top-notch bandwidth.
  • Enhanced NVMe Capabilities – Expect improved performance, reduced latency, and increased concurrent I/O operations.
  • Contemporary CPU Architecture Support – Full compatibility with the latest Intel and AMD processors.
  • Optimised NUMA Handling – Improved memory allocation and CPU affinity management.
  • Enhanced Power Management – More detailed control over CPU states and energy efficiency.
  • Superior Container Performance – Optimised cgroup v2 implementation reduces resource overhead.

Note for Older Hardware: For those utilising outdated systems (over a decade old), perform thorough compatibility checks. Certain older AMD Opteron and Turion CPUs might encounter “illegal instruction” errors when working with Ceph due to absent CPU instruction sets.

Your Comprehensive Upgrade Roadmap

Are you prepared to elevate your environment to Proxmox VE 9.0? Prepare yourself for a command-line challenge. This isn’t for the faint-hearted; it’s a complete distribution upgrade that may even give seasoned Debian users a run for their money.

Before You Begin: This upgrade demands confidence and solid backups. Double-check everything, backup important data multiple times, and be ready for anything (just a little jest, mostly).

Pre-Upgrade Essentials (Follow Closely)

  1. Upgrade to Proxmox VE 8.4 on ALL nodes first – ensure pveversion shows 8.4.1 or a later version.
  2. Ceph Clusters: Ensure you are running Ceph 19.2 Squid beforehand – verify via the Ceph panel in each node’s Web UI.
  3. Backup Essential Data: Protect all VMs, containers, configurations, /etc/pve, /etc/passwd, /etc/network/interfaces – back up anything crucial.
  4. Sufficient Disk Space: A minimum of 5GB on the root filesystem is recommended, though having 10GB+ free is preferable.
  5. IPMI/Console Access: Be prepared for potential SSH disconnections during the upgrade; have IKVM/IPMI or physical access set up.
  6. Terminal Multiplexer: Utilise tmux or screen to ensure you don’t lose your SSH session.
  7. Test Environment: If possible, execute the upgrade on an identical test rig first.

The Upgrade Steps

Important: Execute the following commands as root on each node within your cluster. Avoid performing this through the web GUI console—it may lead to disconnection.

Step 1: Check with the Pre-flight Checker

pve8to9 --full

This script will be invaluable. Run it, rectify any issues it raises, and repeat until no warnings remain. It checks your setup for possible complications and provides alerts tailored to your configuration.

Step 2: Confirm You’re on the Latest PVE 8.4

apt update
apt dist-upgrade
pveversion

You should see 8.4.1 or later. If not, correct your repository settings and try again. This step is critical for a hassle-free upgrade.

Step 3: Shift Critical Operations

Transfer any VMs that need to remain operational during the upgrade to other nodes with the command:

qm migrate  

Plan your cluster upgrade order wisely, as you can migrate from older PVE versions to newer ones, but not the other way around.

Step 4: Update Repository Settings

sed -i 's/bookworm/trixie/g' /etc/apt/sources.list
sed -i 's/bookworm/trixie/g' /etc/apt/sources.list.d/pve-enterprise.list

This changes your Debian repository references from Bookworm to Trixie. Verify that any Bookworm mentions stay out of all repository files.

Step 5: Add the Proxmox VE 9 Test Repository

cat > /etc/apt/sources.list.d/proxmox.sources << EOF
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-test
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOF

Make sure to delete any obsolete Proxmox VE 8 repositories from /etc/apt/sources.list or /etc/apt/sources.list.d/.

Step 6: Adjust Ceph Repository (For Integrated Ceph Users)

Note: Only for systems using integrated Ceph storage. Skip this if you’re using external Ceph.

cat > /etc/apt/sources.list.d/ceph.sources << EOF
Types: deb
URIs: http://download.proxmox.com/debian/ceph-squid
Suites: trixie
Components: test
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOF

After creating this new sources file, delete the old /etc/apt/sources.list.d/ceph.list.

Step 7: Refresh and Validate Package Index

apt update
apt policy proxmox-ve

Ensure your new repositories are functioning correctly, and check that any old Bookworm sources have been removed. The apt policy command should show the Trixie repositories as higher priority.

Step 8: The Final Line of No Return

apt dist-upgrade

This is it! The upgrade will trigger the download of hundreds of packages and could take anywhere from 5 to 60 minutes based on your hardware. You’ll get prompts regarding configuration files – here’s what to keep in mind:

Configuration File Recommended Action Reasoning
/etc/issue Maintain current option Proxmox generates this file automatically at boot time.
/etc/lvm/lvm.conf Choose maintainer’s version (Yes) Contains vital changes pertinent to PVE.
/etc/ssh/sshd_config Select maintainer’s version (Yes) Updates deprecated settings.
/etc/default/grub Keep existing if altered Preserve any custom kernel parameters.

Step 9: Reboot into the Future

systemctl reboot

Cross your fingers, perhaps engage in a little ritual for the sysadmin gods, and watch as your system boots into Proxmox VE 9.0. The new kernel will activate, and all services will reinstate.

Step 10: Verification Post-Upgrade

pve8to9 --full
pveversion
systemctl status pveproxy
systemctl status pvedaemon
systemctl status pvestatd

Don’t forget to clear your browser cache (Ctrl+Shift+R on Windows/Linux, Cmd+Option+R on macOS) before logging into the web UI. The updated interface may encounter problems if cached assets linger.

Common Challenges & Solutions

GRUB Booting Issues on UEFI+LVM Systems

If your system boots in UEFI mode with root on LVM, ensure you have the correct GRUB installed to avoid boot complications:

[ -d /sys/firmware/efi ] && apt install grub-efi-amd64

This will address a bug that prevents GRUB from booting from LVM, displaying “disk lvmid/… not found” errors in UEFI environments.

Changes in Network Interface Names

The new kernel may identify additional hardware features that could alter interface names. Employ the pinning tool:

proxmox-network-interface-pinning

This utility helps secure network interfaces to consistent names, avoiding configuration hurdles after an upgrade.

LVM Auto-activation Challenges

For shared LVM environments, deactivate auto-activation to avert cluster conflicts:

/usr/share/pve-manager/migrations/pve-lvm-disable-autoactivation

This is particularly vital for iSCSI and Fibre Channel shared storage to prevent failures in guest creation and migration.

NVIDIA vGPU Compatibility Issues

Before upgrading, ensure you are utilizing GRID version 18.3 or higher (driver 570.158.02). Older versions may not be compatible with kernel 6.14, which could lead to system instability.

Container Compatibility (cgroupv1 is Deprecated)

Containers using systemd version 230 or earlier (like CentOS 7, Ubuntu 16.04) are no longer supported. The cgroupv1 environment has been entirely removed in PVE 9. Transition these containers to modern distributions while you still have PVE 8 support until July 2026.

Third-party Storage Plugin Updates

External storage plugins must be upgraded by their developers for compatibility with PVE 9. Always consult with plugin maintainers before upgrading production systems reliant on custom storage solutions.

Post-Upgrade Enhancements

Modernise Your Repository Setup

apt modernize-sources

This will transition your old .list files into the new deb822 format. Answer “n” for a preview of changes, and then run it again with “Y” to implement. Your old files will be saved as .bak versions.

Explore New Functionalities

  • Test the new snapshot capabilities on your block storage solutions.
  • Implement HA rules for improved resource management and failover handling.
  • Initiate SDN fabrics for more intricate networking configurations.
  • Check out the revamped mobile UI for easier management while away.
  • Experiment with the enhanced container performance and cgroup v2 functionalities.

Performance Optimisation

With the introduction of the new kernel, consider reviewing:

  • CPU governor settings for improved energy management.
  • NUMA topology configurations suited for large systems.
  • Storage I/O schedulers relevant to your specific workloads.
  • Network tuning parameters necessary for high-throughput applications.

Troubleshooting Common Scenarios

Upgrade Encountered “proxmox-ve” Package Removal Warning

This indicates an issue with your repository configuration. Confirm all Bookworm references have been changed to Trixie, and ensure the PVE 9 repository is correctly set up.

Failure to Boot Post-Upgrade

If the system doesn’t boot, engage rescue mode to:

  1. Inspect GRUB settings using update-grub.
  2. Confirm kernel installation with dpkg -l | grep pve-kernel.
  3. Check /var/log/dpkg.log for upgrade-related errors.

Web UI Not Loading

  1. Clear the browser’s entire cache.
  2. Examine pveproxy service: systemctl status pveproxy.
  3. Restart web services: systemctl restart pveproxy pvedaemon.
  4. Identify any certificate issues in /var/log/daemon.log.

Conclusion

Proxmox VE 9.0 is more than just an update; it represents a significant leap forward in the platform’s evolution. With vendor-agnostic snapshots, advanced high availability features, improved networking capabilities, and a versatile kernel that meets demanding workloads, this release positions Proxmox as the leading open-source virtualization solution.

The upgrade process is not trivial—it’s not something you should tackle during your lunch break. However, for those willing to embrace the challenge, the benefits are numerous, including enhanced performance, a wealth of new features, and increased stability, along with the satisfaction of mastering Proxmox VE 9.0.

Pro Tip: Test the upgrade in a lab setting first. Clone your production setup, experiment with potential failures, and learn before applying what you’ve discovered to the real scenario. Your future self will appreciate the foresight when things go smoothly in production.

Are you ready to step into the future of virtualization? Proxmox VE 9.0 awaits. Happy managing, you illustrious infrastructure specialists!

Key Resources & Documentation

Official Proxmox Documentation

Community Resources

Related Debian Documentation

Storage & Virtualisation References

Reminder: Always consult the official Proxmox documentation for the most current information, especially during beta phases when features and processes may frequently change.



This article draws upon information and materials from several online sources. We acknowledge the contributions of all original authors, publishers, and websites. While every effort has been made to credit the original sources appropriately, any unintended oversight does not constitute a copyright infringement. All trademarks, logos, and images mentioned are owned by their respective parties. If you believe that any content used herein infringes your copyright, please contact us immediately for review and prompt action.

This article is meant solely for informational and educational purposes and does not violate the rights of copyright holders. If any copyrighted material has been used without proper attribution or in violation of copyright laws, it is unintentional, and we will promptly rectify it following notification. Note that the republishing, redistribution, or reproduction of any part or all of the contents in any form is prohibited without express written permission from the author and the website’s owner. For permissions or further inquiries, please get in touch with us.