Editorial desk
Proxmox Lab Editorial
The editorial desk that publishes Proxmox Lab. It is a byline for the site's editorial process, not a person, and this page carries no author biography because there is no individual author to describe.
How this desk works
- Articles are researched from primary sources: vendor and project documentation, published standards and specifications, release notes, advisories, and measurements published by the people who took them.
- Drafts are produced with AI assistance and then edited against those same sources before publication.
- Nothing published here claims hands-on lab testing, benchmarking, or first-hand measurement. Where a figure comes from a datasheet or someone else's test, the article names the source.
- Corrections go to editor@proxmoxlab.org and are made on the affected page. Funding is set out on the disclosure page.
Posts (4)
- virtualization
Proxmox LXC vs VM Explained: Which to Use and When
Proxmox LXC vs VM explained: containers share the host kernel and cost little to run; VMs add isolation, live migration and any OS. When to use each.
- migration
VMware vSphere to Proxmox VE Migration: Licensing & Paths
Plan a VMware vSphere to Proxmox VE migration: licensing scope, ESXi import limits, OVF move paths, guest drivers, cutover checks, and rollback.
- cluster-design
Proxmox No Quorum (500): Diagnose and Fix Corosync
Diagnose Proxmox cluster not ready/no quorum (500) errors with pvecm status, Corosync checks, QDevice guidance, and safe single-node recovery steps.
- cluster-design
Proxmox VE Cluster Planning: Quorum, Storage, Network
Plan a Proxmox VE cluster with two-node QDevice voting, redundant Corosync links, shared storage, Ceph capacity, and recovery when quorum is lost.