Proxmox Level 2 – Engineering

This module takes learners beyond day-one Proxmox administration and into the underlying engineering model: where configuration lives, how guests are launched, how networking is defined, how clustering works, and how to use the CLI for operational support.

Course purpose

Build a deeper operational understanding of Proxmox VE so engineers can work confidently beyond the GUI, understand how the platform is put together, and troubleshoot hosts and guests with more precision.

Duration

2 days
or 1 intensive day if learners are already experienced

Target audience

Infrastructure engineers
Virtualisation administrators
Linux systems engineers supporting Proxmox VE
Technical support staff responsible for troubleshooting hosts and guests

Prerequisites

Learners should already be comfortable with:

basic Linux shell usage
basic Proxmox GUI usage
basic VM and container concepts
IP networking fundamentals

Learning outcomes

identify the main Proxmox configuration and storage locations on disk
explain how Proxmox uses KVM/QEMU for VMs and LXC for containers
manage guests using qm and pct
read and interpret guest configuration files
explain how snapshots work and why long-lived snapshots are usually a poor operational choice
understand cluster membership and core pvecm workflows
perform backup and restore tasks with vzdump
identify key Proxmox services and know when service restarts are safe and appropriate

Detailed module structure

Unit 1: Proxmox architecture and filesystem layout

Topics:

Proxmox VE architecture overview
relationship between Debian, Proxmox services, KVM/QEMU and LXC
important directories and what they contain
- /etc/pve
- /etc/network/interfaces
- /var/lib/pve
- storage-related mount points and metadata locations
how clustered configuration differs from standard local Linux configuration

Lab ideas:

inspect live node layout
compare local files vs cluster-managed files
identify where guest configs, storage definitions and network settings live

Unit 2: Proxmox networking in practice

Topics:

Linux bridge model in Proxmox
physical NICs, bridges, VLANs, bonding and host addressing
reading and editing /etc/network/interfaces
common network layouts for management, guest traffic, storage and cluster traffic
failure modes caused by incorrect network changes

Lab ideas:

create a bridge-backed network layout
add VLAN-aware bridge configuration
troubleshoot a deliberately broken interface definition

Unit 3: How VMs actually run: KVM/QEMU internals

Topics:

what KVM is
what QEMU does
how Proxmox launches and manages VMs
VM process model on the host
guest disks, virtual hardware, machine types and emulation layers
what happens during guest boot from the host perspective

Lab ideas:

inspect running QEMU processes
map VM configuration to the running process
trace a VM from config file to active process

Unit 4: How LXC works

Topics:

containers vs virtual machines
Linux namespaces and cgroups at a practical level
how Proxmox uses LXC
LXC filesystem layout and configuration
operational limits and security considerations of containers

Lab ideas:

create a container via CLI
inspect container config
compare VM and container resource isolation

Unit 5: Guest management from the command line

Topics:

using qm to manage VMs
using pct to manage containers
starting, stopping, migrating and inspecting guests
guest configuration files and parameters
when CLI is preferable to GUI administration

Lab ideas:

create and modify a VM using qm
create and modify a container using pct
inspect guest config files and match them to runtime behaviour

Unit 6: Snapshots — what they are and why they become a problem

Topics:

what a snapshot captures
storage-level vs guest-consistent considerations
performance impact
storage growth and fragmentation
operational risk of keeping snapshots for too long
backup vs snapshot: why they are not the same thing

Important framing: snapshots are useful short-term operational tools, but long-lived snapshots are usually a bad idea in production.

Lab ideas:

create a snapshot
observe changed storage behaviour
review a scenario where snapshots create operational risk

Unit 7: Cluster operations with pvecm

Topics:

what clustering provides in Proxmox
quorum and cluster communications
using pvecm to inspect and manage the cluster
common cluster configuration files
node join/remove concepts
basic split-brain and quorum risk awareness

Lab ideas:

inspect cluster status
review cluster membership
simulate node communication loss and discuss expected behaviour

Unit 8: Backup and restore with vzdump

Topics:

backup types and modes
using vzdump from CLI
scheduling concepts
backup storage targets
restore workflows
common restore pitfalls

Lab ideas:

back up a VM and a container
restore to alternate IDs
validate restored guest configuration

Unit 9: Proxmox services and operational restarts

Topics:

key Proxmox services and their roles
how GUI/API, cluster, statistics and guest management services interact
when a service restart is low risk
when a restart may impact management access or cluster operations
using logs to validate service health

Lab ideas:

inspect service status
restart selected management services safely
correlate service faults with observed GUI/CLI symptoms

Assessment

Short CLI exercise

identify config locations
inspect a VM config
interpret cluster status
run a backup command

Troubleshooting scenario

“A guest exists but won’t start; where do you look first?”

Deep platform understanding - Practical CLI workflows - Real operational confidence

Ideal for engineers who need to support, troubleshoot and operate Proxmox properly

Training scope and tailoring

The training plan shown above is provided as a structured guide to the typical scope and direction of the course. Our training content is reviewed and refined over time, so the precise balance of modules, examples and exercises may vary when the course is delivered.

Where there are specific topics, technologies or operational outcomes that are particularly important to your team, these can normally be incorporated into the delivery plan by prior agreement. Training is not treated as a rigid, fixed package; it is adapted where appropriate to reflect the client environment, delegate experience level, group size and the objectives agreed in advance.