Blog
It has now been several weeks since the release of Debian 13 (Trixie), yet Proxmox still does not provide an official LXC container template for it. While Debian 13 was still in its final freeze phase, I had already created an early beta template ( debian-13-standard_13.x-beta_lxc_proxmox_amd64.tar.gz ) so both I and others could start testing early. Since then, many of you have asked for a proper final version. With Debian 13 now officially released, I’ve prepared a clean and stable template to share with the community. Debian 13 (Trixie) LXC Template for Proxmox This LXC image is based on the official Proxmox Debian 12 (Bookworm) container template, which has been upgraded in place to Debian 13 (Trixie). The result is a lightweight, ready-to-use LXC template that behaves exactly like the official Proxmox images and works seamlessly on both Proxmox 8 and Proxmox 9. To get started with Debian 13 inside containers, simply place the template into your Proxmox .... [read more]
Managing Proxmox storage resources at scale has traditionally been a cumbersome task. In clustered environments where consistency, reliability, and speed are critical, manually adding or removing storage definitions on each node wastes valuable time and introduces the risk of human error. Imagine configuring NFS shares, CephFS mounts, iSCSI targets or Proxmox Backup Server repositories across dozens or even hundreds of nodes, each in different locations, and having to repeat the same steps manually or with ad-hoc scripts. It slows down operations, disrupts automation pipelines, and often leads to inconsistencies between nodes. Until now, there was no clean, supported, and API-driven way to manage storage across Proxmox environments directly within Ansible. This is exactly the gap the new proxmox_storage module fills and finally provides an API-driven storage management for Proxmox based systems. Recently added to the upstream community.proxmox Ansible collection, this module introduces a structured and reliable approach to provisioning storage .... [read more]
The Proxmox ecosystem has grown massively in recent months – and one of the key reasons behind this growth is the strong and active community that continues to push the project forward after the VMware aquisition by Broadcom. You can really feel the momentum. There is a lot happening around Proxmox, and the pace is only picking up. I see this every day in my own work. Proxmox has become one of the most important parts of my tech stack. It’s reliable, flexible, and can be used in so many different ways. Some use it in the classic ClickOps style through the UI. Others build semi-automated setups by using the tools Proxmox already provides. And then there are the fully automated deployments, which is where things really get interesting. That’s especially true if you’re moving away from other virtualization solutions. When you have multiple clusters, running in different locations and .... [read more]
On September 25th, 2025, the Dutch Proxmox Day returns to Ede, Netherlands—bringing together Proxmox users, operators, and developers from across Europe. This community-driven conference focuses entirely on Proxmox VE, real-world cluster operations, and modern virtualization workflows. Organized by Tuxis B.V., a long-time contributor to the Proxmox ecosystem, the event is completely free to attend thanks to its sponsors CT and KPN. The Dutch Proxmox Day has become one of the most important Proxmox-focused community events in Europe. What to Expect at Dutch Proxmox Day 2025 This year’s speaker lineup is packed with well-known names: Tuxis B.V. Proxmox GmbH credativ GmbH Veeam European Space Agency (ESA) From technical deep-dives to real-world cluster challenges, you’ll hear firsthand how Proxmox is being used across industries – from data centers to satellites. ProxLB Talk: Automated Load Balancing for Proxmox Clusters Okay, here’s something I’m personally excited about: this year’s conference will feature a talk .... [read more]
Proxmox VE 9 Beta 1 has been released and represents a major step forward for the Proxmox virtualization platform. For the first time, Proxmox VE is built on Debian 13 “Trixie”, providing a modern and future-proof operating system base while preserving the stability and predictability Proxmox is known for. This beta release introduces several long-requested features, most notably native virtual machine snapshots for block-based storage such as iSCSI and Fibre Channel. Together with substantial improvements in software-defined networking, replication, and overall usability, Proxmox VE 9 clearly targets more advanced and enterprise-grade virtualization environments. Upgrading from Proxmox VE 8.4 is designed to be smooth and well-controlled, allowing existing installations to transition without disruption. In this article, we take a closer look at the most important features and architectural changes introduced with Proxmox VE 9 Beta 1. Key Features in Proxmox VE 9 Native Block Storage Snapshots for iSCSI and Fibre Channel .... [read more]
Over the last few months, I’ve repeatedly been asked how I test my Ansible modules and ProxLB setup in a fully automated and reproducible way. When developing new features or debugging complex behavior, having a clean, quickly deployable Proxmox instance is essential. The same question usually follows: how can Proxmox be deployed without walking through the ISO installer step by step? And is there something like a Proxmox cloud image that can be booted just like Ubuntu or Debian? Testing and Automating Proxmox Deployments Until now, there was no real out-of-the-box solution that was both fast and automation-friendly. That’s why I built exactly that: a prebuilt, ready-to-use Proxmox VE 8.4 image designed for automated cloud deployments and bare-metal auto installations. These images are self-created and not officially provided by Proxmox. Use them at your own risk. They allow consistent testing, rapid provisioning, and seamless integration into automation pipelines using tools .... [read more]
Managing Proxmox VE subscription licenses at scale is a long-standing pain point for administrators. In enterprise environments, manually assigning licenses across dozens or hundreds of nodes is slow, error-prone, and nearly impossible to audit properly. With the new proxmox_node Ansible module, Proxmox license and node management can now be automated end-to-end using the official API—bringing subscriptions, power control, and certificates into modern Infrastructure as Code workflows. The proxmox_node Module The proxmox_node module, now part of the community.proxmox Ansible collection, enables full lifecycle management of Proxmox VE nodes through the official API. Key capabilities include: Bulk import and management of Proxmox subscription licenses Node power state control (start, shutdown, Wake-on-LAN) DNS configuration SSL / TLS certificate management Full support for Ansible check_mode (dry runs) This allows Proxmox node configuration, licensing, and maintenance tasks to become fully automated, repeatable, and version-controlled as Infrastructure as Code. Examples In this section, you can find .... [read more]
When it comes to virtualization, many administrators still believe that NFS is not suitable for serious enterprise workloads and that protocols like iSCSI or Fibre Channel are required to achieve acceptable performance. While this assumption may have been true years ago, modern infrastructure tells a very different story. With fast networking becoming the norm, protocol efficiency and latency matter far more than raw bandwidth alone. NFS is often underestimated due to outdated assumptions or suboptimal configurations. In many Proxmox environments, NFSv3 is still used by default, which often leads to unnecessary performance limitations. Latencies by Storage Type Before comparing NFSv3 and NFSv4 directly, it is useful to establish a general baseline of latency expectations across different storage technologies commonly used with Proxmox. This overview helps put the later benchmark results into perspective and shows where NFS typically sits compared to block-based and NVMe-backed solutions. Latency overview of different storage types .... [read more]
Running your own on-prem PKI (Public Key Infrastructure) can be a game-changer and it’s not just for enterprises, but also for advanced homelabs. Whether it’s about securing internal services, managing client certificates for S/MIME email encryption, or just having full control over certificate issuance, operating your own root CA brings a lot of flexibility and independence. There are many ways to set up a basic CA, even just using OpenSSL on the command line. But as soon as your setup grows, you’ll quickly run into limitations. Things like revoking certificates, publishing CRLs, using OCSP, or automating issuance via the ACME protocol become essential. And that’s where more powerful tools come in. Popular solutions like FreeIPA, HashiCorp Vault, or EJBCA offer robust PKI functionality, but they can be overkill for some environments or tricky to integrate with specific workflows. One tool that’s gained a lot of traction in recent years is .... [read more]
Automating Proxmox VE cluster creation has long meant fragile shell scripts, manual SSH steps, and hard-to-debug Ansible hacks. With the new native Ansible modules proxmox_cluster and proxmox_cluster_info , you can now create and join Proxmox clusters cleanly via the official API—fully idempotent, error-aware, and ready for real-world automation. Both modules use the official Proxmox VE API, allowing reliable and fully supported cluster creation and join operations. They are already part of the upstream Ansible Community Proxmox collection and offer robust error handling as well as support for password-based and token-based authentication. Usage This section explains how to use the new Ansible modules to automate Proxmox cluster creation and joining with minimal configuration. Using these modules is intentionally simple and requires only a single Ansible task to either create a new Proxmox VE cluster or join an existing one. Create a Proxmox VE Cluster Creating a Proxmox VE cluster can now .... [read more]
Previous Next