Recent submissions

Comment · 9 months ago
As Proxmox environments grow, keeping track of capacity, hot spots, and maintenance windows gets painful. PegaProx aims to reduce that friction by acting as a single source of truth for clusters, nodes, storage, and metrics without relying on fragmented tooling.
Comment · 9 months ago
ProxLB is an open-source 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.
Comment · 9 months ago
Really happy to hear, thanks!
Comment · 9 months ago
Incus has proven to be a strong and modern platform for managing containers and virtual machines, and it can run BSD virtual machines just as easily as Linux ones. With its built in QEMU support and well maintained BSD cloud images, FreeBSD, NetBSD, and OpenBSD can be launched directly in Incus without a manual installation and with familiar workflows. This makes Incus an efficient and reliable choice for testing, development, and running BSD systems in a lightweight lab or cloud style environment.
Comment · 10 months ago
Sylve (by Alchemilla and sponsored by the FreeBSD Foundation) is an open-source project that tries to make virtualization on FreeBSD simple and user friendly. It uses Bhyve for virtual machines, Jails for containers and takes advantage of ZFS for storage. The backend is written in Go and the frontend in SvelteKit, which gives it a clean and modern look. The idea behind it is to provide something similar to Proxmox but made for FreeBSD - including clustering support which lacks in most UI stuff (yes, cbsd can it on the cli).
Comment · 10 months ago
ProxCLMC 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 guessing, maintaining spreadsheets, or breaking migrations at 2 a.m., you get a deterministic result you can directly use when selecting VM CPU models.

Other virtualization platforms solved this years ago with built-in mechanisms (think cluster-wide CPU compatibility enforcement). Proxmox VE doesn’t have automated detection for this yet, so admins are left comparing flags by hand. ProxCLMC fills exactly this missing piece and is tailored specifically for Proxmox environments.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton