Blog
PegaProx is designed to be the central control point for modern Proxmox VE based datacenters. It brings together everything administrators need to manage complex infrastructures in a single, clear interface, similar to what many operators already know from established enterprise virtualization platforms. Instead of switching between clusters, nodes, storage views, and monitoring tools , PegaProx provides a real unified platform that delivers full visibility and precise control over the entire environment - watch the demo , now! This article is an independent technical overview of PegaProx. The official product website is pegaprox.com . Virtualization operators often face recurring challenges in day to day operations. Keeping track of resource usage across multiple clusters, identifying overloaded nodes before performance degrades, coordinating maintenance windows, and ensuring workloads remain highly available can quickly become complex. As environments grow, manual processes and fragmented tooling increase the risk of configuration drift, human error, and unexpected downtime. .... [read more]
This post describes how to export metrics from bhyve based virtual machines and Jails managed by Sylve on FreeBSD by my Prometheus exporter. The focus is on collecting reliable data from the host system without relying on tooling that was primarily designed for Linux hypervisors or assumes the existence of hypervisor level counters. Monitoring bhyve workloads on FreeBSD is different from monitoring virtual machines on other platforms. bhyve virtual machines run as regular userland processes and typically use ZFS datasets or zvols for storage. As a result, many of the metrics that are commonly available on other hypervisors do not exist in the same form on FreeBSD. This often leads to confusion when trying to apply standard monitoring approaches that expect per vCPU statistics or detailed hypervisor telemetry. While this is easily possible in Proxmox VE , this was missing for me in bhyve. Despite these differences, there is still .... [read more]
Snapshots are one of the most useful safety mechanisms in virtualized environments. They make it easy to roll back changes, reduce risk during upgrades, and provide confidence when testing or migrating workloads. Proxmox VE supports snapshots for both virtual machines and containers, and on a single guest level this works well and reliably. The problem starts once a setup grows into a real Proxmox VE cluster. There is no native way to get a complete overview of snapshots across all nodes in a cluster. Simple but important questions are surprisingly hard to answer. Which nodes currently have snapshots? Which VMs or containers still carry old snapshots? How many snapshots exist in total and how old are they? Answering these questions usually means clicking through every node and every guest manually. Over time, snapshots tend to pile up quietly. A snapshot created before a quick change or update is often forgotten. .... [read more]
Two years ago I started working on a project called ProxLB because something essential was missing in my daily work with Proxmox VE based clusters. At that time I was deeply involved in my BoxyBSD project which provides free VPS instances for people who are interested in BSD systems. Running such an environment made it very clear that a DRS like resource scheduler was needed to keep workloads balanced and clusters healthy. Since there was no solution available that matched these needs I decided to build one myself. ProxLB was publicly released on the seventh of July in 2024 and introduced a first functional version of a DRS like scheduler for Proxmox VE . After announcing the project on Reddit and several other platforms the feedback was overwhelming. Many users quickly pointed out features that were missing at that time and also shared ideas based on their real world usage. .... [read more]
ProxLB is a lightweight load-balancing and placement helper designed for Proxmox VE environments, helping operators make smarter scheduling and availability decisions for virtual machines and containers. It provides advanced features such as pinning, affinity and anti-affinity rules, maintenance mode, and intelligent node selection to keep workloads where they belong. With a strong focus on simplicity and native integration, ProxLB enhances cluster resilience while remaining easy to deploy and operate. ProxLB 1.1.11 Release Today (2026-01-12), I released version 1.1.11 of ProxLB , a release that focuses on deeper integration, smarter decision-making, and more predictable operations in Proxmox VE clusters. This version introduces a streamlined integration with Proxmox’s native HA rules and affinity/anti-affinity stack (currently in beta), allowing ProxLB to work more naturally with existing placement constraints instead of re-implementing them. As a result, operators can combine native Proxmox concepts with ProxLB 's balancing logic in a more transparent and consistent way. .... [read more]
With Proxmox Backup Server 4 , a long-awaited feature has finally arrived: native support for S3-compatible object storage as a datastore. This fundamentally expands how backups can be designed, stored, and scaled in Proxmox environments. Until now, Proxmox Backup Server required local disks or locally attached storage to host datastores. With version 4, this limitation is gone. Datastores can now be backed by any S3-compatible backend, making it possible to use self-hosted object storage solutions such as MinIO , SeaweedFS , or Garage , as well as public or private S3 offerings, while still benefiting from all core PBS features like deduplication, compression, encryption, pruning, verification, and garbage collection. One of the biggest advantages of this approach is that no local storage is required on the Proxmox Backup Server itself anymore. PBS becomes a lightweight, stateless service layer that handles backup orchestration and metadata, while the actual backup data resides .... [read more]
Live migration is one of the most powerful and frequently used features in a Proxmox VE cluster, but it relies on a prerequisite that is often underestimated: consistent CPU compatibility across all nodes. In real-world environments, clusters rarely consist of identical hardware where we could simply use the host type. Nodes are added over time, CPU generations differ, and feature sets evolve. While Proxmox VE allows flexible CPU configuration, determining a safe and optimal CPU baseline for the entire cluster is still largely a manual and experience-driven task. ProxCLMC (Prox CPU Live Migration Checker) was created by gyptazy to close this gap in a simple, automated, and reproducible way. It inspects all nodes in a Proxmox VE cluster, analyzes their CPU capabilities, and calculates the highest possible CPU compatibility level that is supported by every node. Instead of relying on assumptions, spreadsheets, or trial and error, operators receive a clear .... [read more]
BoxyBSD started as a simple idea. Lowering the barrier of entry into the BSD world. What began in late 2022 on spare hardware has grown into a globally distributed, fully automated, free VPS platform that allows beginners and newcomers to explore BSD systems without needing a credit card, prior infrastructure knowledge, or their own hardware. Where was the talk given? This talk was given on December, 11th at the Virtualization Gathering hosted by the credativ GmbH in Mönchengladbach, Germany. You may also find another talk of my ProxWall project at the upcoming event. The BoxyBSD Hypervisor Migration Talk In this talk, I walk through the journey of BoxyBSD as it really happened. Not as a polished success story, but as an honest look at what it takes to operate a non-commercial and educational hosting platform at scale. From early experiments with FreeBSD jails and bhyve, through painful scaling limitations, to .... [read more]
The Proxmox Datacenter Manager 1.0 brings something many administrators have wanted for a long time. A single place where all Proxmox VE clusters, individual nodes and Proxmox Backup Server instances come together. Instead of jumping through different interfaces, everything appears in one central cockpit. You get a clear and consistent overview of hosts, VMs, containers and datastores, even when they are spread across multiple locations. The built in search makes it easy to find the right resources quickly, even in very large environments. Progress Is Happening, Just Not Fast As the Proxmox Datacenter Manager just got released in version 1.0 the major question is what happened during almost a year of development? Let me spoiler, I’m disappointed! Maybe you already had a look at my initial post about the Proxmox Datacenter Manager when the first alpha version got released and my thoughts about it during the beta version. Now, we .... [read more]
Creating a highly secure Proxmox cluster with proper micro segmentation has become one of the most frequent topics in my discussions with users and customers. Almost every organization that migrates from another virtualization platform asks the same question early on. How can network segments be defined and enforced directly inside Proxmox in a simple and centralized way? For a long time, there was no real answer to this. While Proxmox is extremely powerful and flexible, micro segmentation was never available as a native, integrated solution. Most approaches relied on external firewalls, complex network designs, or additional tooling that did not feel like a natural part of Proxmox. This is exactly the gap that my ProxWall project is intended to close. The motivation behind ProxWall reminds me strongly of the early days of my ProxLB project. Back then, many Proxmox users were searching for a real dynamic workload scheduler that could .... [read more]
Next