This document details the configuration of virtual machines hosted on the Proxmox server.
The Proxmox server hosts a single virtual machine:
| VMID | Name | Status | Memory (MB) | Boot Disk (GB) | PID |
|---|---|---|---|---|---|
| 100 | ubuntu | running | 39000 | 450.00 | 2044 |
agent: 1,freeze-fs-on-backup=0,fstrim_cloned_disks=1
balloon: 0
boot: order=scsi0;net0
cores: 6
cpu: host
hostpci0: 0000:01:00.0,x-vga=1
hostpci1: 0000:01:00.1
memory: 39000
meta: creation-qemu=9.0.2,ctime=1738027536
name: ubuntu
net0: virtio=BC:24:11:73:B7:A5,bridge=vmbr0,firewall=1
numa: 1
onboot: 1
ostype: l26
parent: autosnap-2025-02-27
scsi0: NVME:vm-100-disk-0,discard=on,size=450G
scsi1: local-lvm:vm-100-disk-1,size=244G
scsihw: virtio-scsi-single
smbios1: uuid=5aa3c82d-c8c4-43ba-875b-791df1512d60
sockets: 1
vga: qxl
vmgenid: 8d41ce50-d4c2-4a40-bbcc-1c86269d8780
| Resource | Allocation | Details |
|---|---|---|
| CPU | 6 cores, 1 socket | Uses host CPU type (passthrough) |
| Memory | 39000 MB (38.1 GB) | No ballooning (fixed memory allocation) |
| Primary Disk | 450 GB | Located on NVME ZFS pool with discard enabled |
| Secondary Disk | 244 GB | Located on local-lvm thin pool |
| GPU | PCIe Passthrough | Primary GPU (0000:01:00.0) with VGA function |
| GPU Audio | PCIe Passthrough | GPU audio device (0000:01:00.1) |
| Network | virtio | Bridge vmbr0, MAC: BC:24:11:73:B7:A5, firewall enabled |
| BIOS | OVMF (UEFI) | UUID: 5aa3c82d-c8c4-43ba-875b-791df1512d60 |
| Feature | Setting | Description |
|---|---|---|
| QEMU Agent | Enabled | Guest-side agent for better integration |
| Freeze FS on Backup | Disabled | Does not freeze filesystem during backup |
| TRIM Cloned Disks | Enabled | Enables TRIM on disk clones for better SSD performance |
| Disk Discard | Enabled | Allows VM to issue TRIM/discard commands to underlying storage |
| Auto-start | Enabled | VM starts automatically when Proxmox boots |
| Ballooning | Disabled | Memory is fixed at 38.1 GB |
| NUMA | Enabled | Single NUMA node configuration |
VM 100 is configured to use snapshots for backup purposes. Currently, the VM is running from a state that is a descendant of snapshot autosnap-2025-02-27.
The VM has a history of snapshots, though most are now deleted and only visible in the configuration history. These snapshots follow a naming pattern of autosnap-YYYY-MM-DD and are created by an automated script.
The VM is connected to the Proxmox host's bridge network:
| Interface | Type | MAC Address | Bridge | Firewall |
|---|---|---|---|---|
| net0 | virtio | BC:24:11:73:B7:A5 | vmbr0 | Enabled |
The bridge vmbr0 connects directly to the host's physical network interface eno1.
The VM uses two different storage types:
Primary Disk (Boot):
Secondary Disk:
The VM is configured with PCIe passthrough for GPU functionality:
| PCIe Device | Function | Options |
|---|---|---|
| 0000:01:00.0 | GPU | x-vga=1 (primary graphics device) |
| 0000:01:00.1 | GPU Audio | None |
This configuration suggests the VM is being used for graphics-intensive applications or gaming, with direct access to a physical GPU.
The boot order for the VM is configured as follows:
The VM uses QEMU version 9.0.2 for virtualization with the following special settings:
The VM has an automated snapshot management process. Looking at the snapshot script (/scripts/snapshot.sh), we can see:
autosnap-YYYY-MM-DDBased on the configuration, this is a high-resource VM with:
The VM configuration includes several performance optimizations: