Proxmox VE Hypervisor

This command produces directly from Proxmox the list of VMs with their current state, their auto-start policy (onboot) and their resume order (startup) — without confusing the instantaneous state (running / stopped) with the persistent configuration.

for vmid in $(qm list | awk 'NR > 1 {print $1}'); do
    config=$(qm config "$vmid")

    name=$(awk -F': ' '/^name:/ {print $2}' <<< "$config")
    status=$(qm status "$vmid" | awk '{print $2}')
    onboot=$(awk -F': ' '/^onboot:/ {print $2}' <<< "$config")
    startup=$(awk -F': ' '/^startup:/ {print $2}' <<< "$config")

    [ -z "$onboot" ] && onboot=0
    [ -z "$startup" ] && startup="-"

    printf '%-6s %-30s status=%-8s onboot=%-2s startup=%s\n' \
        "$vmid" "$name" "$status" "$onboot" "$startup"
done

205    205-Ubuntu-Nextcloud           onboot=1  startup=order=40,up=30,down=60
210    210-IA-CORE-CUDA               onboot=1  startup=order=20,up=30,down=60
215    215-IA-Services                onboot=1  startup=order=10,up=60,down=60
260    260-W11-CUDA-Ollama            onboot=0  startup=-
300    300-n8n                        onboot=1  startup=order=30,up=30,down=60
…      environnements à la demande    onboot=0  startup=-

• Proxmox VE administration (web UI + CLI)
• Creation, configuration and management of KVM/QEMU VMs
• ZFS storage management via Proxmox
• Creation of reusable system templates
• Proxmox snapshots (vzdump) — not yet an independent backup
• VM cloning for rapid deployment
• Hypervisor troubleshooting (logs, VNC console)

Cloning an old template revealed a residual hostname. The clone was fixed and checked, then the generic template was rebuilt from an official ISO to explicitly control its content. The build VM was sanitized before conversion: machine identity, hostname, SSH keys, network, Cloud-Init state and logs were cleaned.

A full validation clone confirmed Cloud-Init initialization, generation of a clean identity, networking, DNS, SSH, the guest agent, and persistence after reboot. The old template was only replaced after this check; the ZFS origins were verified before deleting the candidate that had become redundant, to preserve VM independence.

A template is not worth much for its cloning speed but for the mastery of what it transmits (system, identity, network, access, initialization). Building, validating and replacing are three separate operations: the old template stays available until its replacement and its validation clone have met every criterion.

Source système vérifiée
        │
        ▼
VM temporaire de construction
        │ installation et configuration du socle
        ▼
Neutralisation
        │ identités, réseau, secrets et journaux
        ▼
Template temporaire
        │
        ▼
Clone de validation
        │ contrôles fonctionnels et d'indépendance
        ▼
Template validé
        │
        ├── clone complet → VM applicative
        └── template dérivé → socle spécialisé

An onboard PCIe device intermittently disappeared. The diagnosis distinguished a real absence on the bus from a simple driver fault, by successively checking the interface, the modules, PCIe enumeration, the parent port and the rescan. A full power cycle restored the device; recurrence is being monitored before considering a conditional firmware update.