When reporting a Proxmox issue, collecting relevant diagnostic information is crucial for efficient troubleshooting. The following commands provide comprehensive details about the Proxmox host, cluster, and virtual guests.

ALWAYS Capture

These commands provide general system health and configuration details.

System Information:

    hostnamectl
    uname -a

Proxmox Version Information:

    pveversion -v

Cluster Status and Quorum (if applicable):

    pvecm status
    quorum status

System Services Status:

    systemctl list-units --type=service --state=running
    systemctl status pveproxy pvedaemon pvescheduler pvestatd pve-cluster

Disk Usage:

    df -h

Hardware Information:

    lshw -short
    lscpu
    free -h

Network Configuration:

    ip a
    ip route
    cat /etc/network/interfaces

Journal Logs for Key Proxmox Services:

    journalctl -u pveproxy.service -n 50 --no-pager
    journalctl -u pvedaemon.service -n 50 --no-pager
    journalctl -u pve-cluster.service -n 50 --no-pager

For Storage Issues

These commands provide details specific to storage configurations and status.

    pvesm status

LVM/LVM-thin Information (if in use):

    lvs --all
    vgs --all

ZFS Information (if in use):

    zpool status -v
    zfs list

Ceph Information (if in use):

    ceph status
    ceph osd tree
    ceph health detail

IMPORTANT: If this is a CEPH issue, see the ceph requirements in the Ceph session of the knowledge base and use that instead. 

For Guest (VM/Container) Issues

These commands provide details about virtual machine and container configuration and status.

List All Virtual Guests and Their Status:

    qm list
    lxc list

Specific VM/Container Configuration (replace VMID or CTID):

    qm config <VMID>
    lxc config show <CTID>

Specific VM/Container Status (replace VMID or CTID):

    qm status <VMID>
    lxc info <CTID>

Console Logs for a Specific VM (replace VMID):

    journalctl -u qemu-server@<VMID>.service -n 50 --no-pager

For Cluster Issues

These commands provide additional information relevant to multi-node Proxmox clusters.

Corosync Configuration:

    cat /etc/corosync/corosync.conf

Corosync Logs:

    journalctl -u corosync.service -n 50 --no-pager