ProxMenux/web/messages/en/docs/glossary.json

{
  "meta": {
    "title": "Glossary | ProxMenux Documentation",
    "description": "Definitions of the technical terms used throughout the ProxMenux documentation — Proxmox concepts (VM, LXC, qm, pct, pmxcfs), virtualization fundamentals (KVM, IOMMU, VFIO, OVMF), storage (ZFS, ARC, LVM, vzdump, PBS), network (bridge, VLAN, nftables) and ProxMenux-specific terminology.",
    "ogTitle": "Glossary | ProxMenux Documentation",
    "ogDescription": "Quick reference for the technical terms used across the ProxMenux documentation."
  },
  "header": {
    "title": "Glossary",
    "description": "Definitions of the technical terms used throughout the ProxMenux documentation. Covers Proxmox concepts, virtualization fundamentals, storage, networking, Linux internals and ProxMenux-specific terminology.",
    "section": "Glossary"
  },
  "callout": {
    "title": "How to use this page",
    "bodyRich": "Each entry has a category badge and a short definition. <em>See also</em> links jump to the doc page where the term is most relevant. Use the A–Z navigation below to scroll directly to a letter."
  },
  "jumpHeading": "Jump to letter",
  "seeAlsoLabel": "See also:",
  "aliasesLabel": "also:",
  "missingCallout": {
    "title": "Missing a term?",
    "leadRich": "If a term in the docs is missing, open an issue or PR on <ext>GitHub</ext>. Glossary content lives in <code>web/messages/en/docs/glossary.json</code>, with matching locale catalogs."
  },
  "entries": [
    {
      "term": "ACS",
      "aliases": [
        "Access Control Services",
        "ACS override"
      ],
      "category": "Virtualization",
      "definitionRich": "PCIe access-control features that help isolate device traffic. IOMMU grouping depends on hardware and topology. The <em>ACS override</em> kernel patch can split groups reported by Linux, but does not add hardware isolation; assigning those devices to separate VMs carries a security risk.",
      "seeAlso": [
        {
          "label": "Add Controller or NVMe to VM",
          "href": "/docs/disk-manager/add-controller-nvme-vm"
        }
      ]
    },
    {
      "term": "ARC",
      "aliases": [
        "Adaptive Replacement Cache"
      ],
      "category": "Storage",
      "definitionRich": "ZFS read cache in host RAM, holding recently and frequently used data blocks. Its default limit depends on the Proxmox version and installation settings. ProxMenux Post-Install offers an option to cap it.",
      "seeAlso": [
        {
          "label": "Post-Install: Storage",
          "href": "/docs/post-install/storage"
        },
        {
          "label": "ZFS commands",
          "href": "/docs/help-info/zfs-commands"
        }
      ]
    },
    {
      "term": "Bind mount",
      "category": "Linux",
      "definitionRich": "A Linux feature that exposes one part of the filesystem at another path. ProxMenux uses bind mounts to share host directories with LXC containers via <code>pct set -mpN</code>.",
      "seeAlso": [
        {
          "label": "LXC Mount Points",
          "href": "/docs/storage-share/lxc-mount-points"
        }
      ]
    },
    {
      "term": "Bond",
      "aliases": [
        "Network bond",
        "Link aggregation"
      ],
      "category": "Network",
      "definitionRich": "Combines multiple physical network interfaces into one logical interface — for redundancy (active-backup), throughput (LACP / 802.3ad) or both. Configured in <code>/etc/network/interfaces</code>."
    },
    {
      "term": "Bridge",
      "aliases": [
        "vmbrX",
        "vmbr0",
        "Linux bridge"
      ],
      "category": "Network",
      "definitionRich": "A virtual layer-2 switch on the host. <code>vmbr0</code> commonly connects guests to the physical network. Additional bridges (<code>vmbr1</code>, <code>vmbr2</code>...) can separate guest networks, depending on their physical links and configuration.",
      "seeAlso": [
        {
          "label": "Bridge analysis & guided repair",
          "href": "/docs/network/bridge-analysis"
        }
      ]
    },
    {
      "term": "Ceph",
      "category": "Storage",
      "definitionRich": "Distributed storage integrated with Proxmox for hyper-converged clusters. OSDs (Object Storage Daemons) underpin its object, block and file storage. Required Ceph versions depend on the Proxmox release and upgrade path; consult the corresponding upgrade guide.",
      "seeAlso": [
        {
          "label": "Upgrade PVE 8 to PVE 9",
          "href": "/docs/utils/upgrade-pve8-pve9"
        }
      ]
    },
    {
      "term": "CT",
      "aliases": [
        "Container",
        "LXC container"
      ],
      "category": "Proxmox",
      "definitionRich": "Short for \"container\" — Proxmox terminology for an LXC instance. Has a numeric CTID that maps to <code>/etc/pve/lxc/&lt;CTID&gt;.conf</code>. See also <strong>LXC</strong>.",
      "seeAlso": [
        {
          "label": "VM and CT Management",
          "href": "/docs/help-info/vm-ct-commands"
        }
      ]
    },
    {
      "term": "deb822",
      "category": "Linux",
      "definitionRich": "Modern format for APT repository sources, using <code>.sources</code> files with structured key/value blocks (Types, URIs, Suites, Components, Signed-By). Replaces the legacy single-line <code>.list</code> format. Standard from PVE 9 / Debian Trixie onward.",
      "seeAlso": [
        {
          "label": "Upgrade PVE 8 to PVE 9",
          "href": "/docs/utils/upgrade-pve8-pve9"
        }
      ]
    },
    {
      "term": "dGPU",
      "aliases": [
        "Discrete GPU"
      ],
      "category": "Virtualization",
      "definitionRich": "A separate graphics card, typically connected over PCIe, unlike an <strong>iGPU</strong>. It can be assigned to a VM with VFIO or accessed by multiple LXC containers through device nodes and the host driver, subject to hardware and application support.",
      "seeAlso": [
        {
          "label": "Add GPU to VM (Passthrough)",
          "href": "/docs/hardware/gpu-vm-passthrough"
        }
      ]
    },
    {
      "term": "Dialog",
      "category": "Linux",
      "definitionRich": "ncurses-based tool for drawing menus, prompts and progress bars in a terminal. ProxMenux is built around dialog menus."
    },
    {
      "term": "DKMS",
      "aliases": [
        "Dynamic Kernel Module Support"
      ],
      "category": "Linux",
      "definitionRich": "Framework for rebuilding registered out-of-tree kernel modules, such as NVIDIA or ZFS, when the kernel changes. Successful builds still require compatible module sources and matching kernel headers.",
      "seeAlso": [
        {
          "label": "Install Coral TPU (Host)",
          "href": "/docs/hardware/install-coral-tpu-host"
        }
      ]
    },
    {
      "term": "Fail2Ban",
      "category": "Linux",
      "definitionRich": "Intrusion prevention service that watches log files for repeated authentication failures and bans the offending IPs at the firewall layer. ProxMenux ships pre-configured jails for SSH, the Proxmox UI and the Monitor.",
      "seeAlso": [
        {
          "label": "Fail2Ban",
          "href": "/docs/security/fail2ban"
        }
      ]
    },
    {
      "term": "Fastfetch",
      "category": "Linux",
      "definitionRich": "ASCII-art system info tool that runs on shell login (the \"system summary banner\"). Replaces the older <code>neofetch</code>; available as an opt-in option in ProxMenux Post-Install.",
      "seeAlso": [
        {
          "label": "Post-Install: Optional",
          "href": "/docs/post-install/optional"
        }
      ]
    },
    {
      "term": "GRUB",
      "aliases": [
        "GRand Unified Bootloader"
      ],
      "category": "Linux",
      "definitionRich": "Boot loader used on GRUB-based Linux installations. Configuration is in <code>/etc/default/grub</code> and <code>/boot/grub/</code>; run <code>update-grub</code> after edits. Other Proxmox boot setups may use systemd-boot, so check the active boot loader before changing kernel parameters.",
      "seeAlso": [
        {
          "label": "GPU Passthrough commands",
          "href": "/docs/help-info/gpu-commands"
        }
      ]
    },
    {
      "term": "iGPU",
      "aliases": [
        "Integrated GPU"
      ],
      "category": "Virtualization",
      "definitionRich": "Graphics processor built into the CPU package (Intel UHD / Iris, AMD Radeon Vega in Ryzen APUs). Typically shared across multiple LXC containers via <code>/dev/dri</code> rather than passed through to a single VM.",
      "seeAlso": [
        {
          "label": "Add GPU to LXC",
          "href": "/docs/hardware/igpu-acceleration-lxc"
        }
      ]
    },
    {
      "term": "ifupdown / ifupdown2",
      "category": "Network",
      "definitionRich": "The classic Debian network configuration system that reads <code>/etc/network/interfaces</code>. <code>ifupdown2</code> is the rewritten version Proxmox uses by default — supports live reload via <code>ifreload -a</code>."
    },
    {
      "term": "initramfs",
      "category": "Linux",
      "definitionRich": "Initial RAM filesystem the kernel uses at boot before the real root filesystem is mounted. Contains drivers needed early (storage, encryption, RAID). Rebuilt with <code>update-initramfs -u -k all</code> after VFIO, IOMMU or storage driver changes."
    },
    {
      "term": "IOMMU",
      "aliases": [
        "Input/Output Memory Management Unit",
        "VT-d",
        "AMD-Vi"
      ],
      "category": "Virtualization",
      "definitionRich": "Hardware feature (Intel VT-d / AMD-Vi) needed for PCIe passthrough to VMs. Enable it in firmware and ensure kernel support is active. Kernel arguments such as <code>intel_iommu=on</code> or <code>amd_iommu=on</code> may be needed, depending on platform and kernel defaults.",
      "seeAlso": [
        {
          "label": "Post-Install: Virtualization",
          "href": "/docs/post-install/virtualization"
        },
        {
          "label": "Add GPU to VM (Passthrough)",
          "href": "/docs/hardware/gpu-vm-passthrough"
        }
      ]
    },
    {
      "term": "IOMMU group",
      "category": "Virtualization",
      "definitionRich": "A set of devices that forms the smallest IOMMU isolation boundary. Devices within a group are not necessarily isolated from one another; review every member before VFIO assignment. Listed via <code>find /sys/kernel/iommu_groups/ -type l | sort -V</code>."
    },
    {
      "term": "iSCSI",
      "aliases": [
        "Internet SCSI"
      ],
      "category": "Storage",
      "definitionRich": "Network protocol that exposes block storage over IP — a remote disk appears as a local SCSI device. Registered as Proxmox storage via <code>pvesm add iscsi</code>.",
      "seeAlso": [
        {
          "label": "Add iSCSI target as Proxmox storage",
          "href": "/docs/storage-share/host-iscsi"
        }
      ]
    },
    {
      "term": "KVM",
      "aliases": [
        "Kernel-based Virtual Machine"
      ],
      "category": "Virtualization",
      "definitionRich": "Linux kernel module that turns the host into a hypervisor. Combined with <strong>QEMU</strong> for device emulation, it's the foundation Proxmox uses to run VMs."
    },
    {
      "term": "LVM",
      "aliases": [
        "Logical Volume Manager"
      ],
      "category": "Storage",
      "definitionRich": "Linux volume-management layer that groups physical storage into volume groups (VG) containing logical volumes (LV). LVM-based Proxmox installations commonly use LVM-thin for guest disks; other backends are available. Tools include <code>pvs</code>, <code>vgs</code> and <code>lvs</code>.",
      "seeAlso": [
        {
          "label": "Storage and Disks commands",
          "href": "/docs/help-info/storage-commands"
        }
      ]
    },
    {
      "term": "LXC",
      "aliases": [
        "Linux Containers"
      ],
      "category": "Linux",
      "definitionRich": "OS-level virtualization in which isolated userspace instances share the host kernel. Usually has less overhead than VMs, with a different isolation boundary. Proxmox manages LXC containers with the <code>pct</code> CLI.",
      "seeAlso": [
        {
          "label": "VM and CT Management",
          "href": "/docs/help-info/vm-ct-commands"
        }
      ]
    },
    {
      "term": "Lynis",
      "category": "Linux",
      "definitionRich": "Open-source security auditor (by CISOfy) that scans the host and prints a hardening score plus concrete remediation hints. ProxMenux installs the latest from upstream GitHub rather than the (older) Debian package.",
      "seeAlso": [
        {
          "label": "Lynis",
          "href": "/docs/security/lynis"
        }
      ]
    },
    {
      "term": "MAC address",
      "aliases": [
        "Hardware address"
      ],
      "category": "Network",
      "definitionRich": "Usually a 48-bit Ethernet interface identifier, assigned by hardware or software. ProxMenux <em>Persistent Network Names</em> matches MAC addresses to stable interface names (<code>eno1</code>, <code>enp3s0</code>) to keep names consistent after PCI re-enumeration.",
      "seeAlso": [
        {
          "label": "Persistent interface names",
          "href": "/docs/network/persistent-names"
        }
      ]
    },
    {
      "term": "MOTD",
      "aliases": [
        "Message of the Day"
      ],
      "category": "Linux",
      "definitionRich": "Text displayed after SSH login, stored in <code>/etc/motd</code>. ProxMenux Post-Install can add a banner; the uninstaller restores the previous file when a backup exists."
    },
    {
      "term": "NFS",
      "aliases": [
        "Network File System"
      ],
      "category": "Storage",
      "definitionRich": "Unix-native network file sharing protocol. Registered as Proxmox storage via <code>pvesm add nfs</code>; also usable as an LXC client / server via dedicated ProxMenux flows.",
      "seeAlso": [
        {
          "label": "Storage & Share Manager",
          "href": "/docs/storage-share"
        }
      ]
    },
    {
      "term": "nftables / iptables",
      "category": "Network",
      "definitionRich": "Linux firewall tooling. <code>nftables</code> is the modern framework; <code>iptables</code> can use legacy or nft-compatible backends. Classic <code>pve-firewall</code> uses iptables, while the alternative proxmox-firewall backend uses nftables.",
      "seeAlso": [
        {
          "label": "Network commands",
          "href": "/docs/help-info/network-commands"
        }
      ]
    },
    {
      "term": "nouveau",
      "category": "Linux",
      "definitionRich": "Open-source NVIDIA graphics driver included with the Linux kernel. When installing the proprietary NVIDIA driver, prevent nouveau from binding the same GPU, usually by blacklisting it and rebuilding initramfs.",
      "seeAlso": [
        {
          "label": "NVIDIA installation guide",
          "href": "/guides/nvidia"
        }
      ]
    },
    {
      "term": "no-subscription repo",
      "category": "Proxmox",
      "definitionRich": "Proxmox package repository available without an enterprise subscription. Packages receive less validation than in the enterprise repository, which Proxmox recommends for production. ProxMenux Post-Install offers repository configuration.",
      "seeAlso": [
        {
          "label": "Post-Install: Basic Settings",
          "href": "/docs/post-install/basic-settings"
        }
      ]
    },
    {
      "term": "OVA / OVF",
      "aliases": [
        "Open Virtualization Format"
      ],
      "category": "Virtualization",
      "definitionRich": "DMTF formats for packaging portable VMs. <strong>OVA</strong> packages the files in a single TAR archive; <strong>OVF</strong> describes the VM in XML with accompanying disk files, commonly VMDK. Import support depends on the target hypervisor and configuration.",
      "seeAlso": [
        {
          "label": "Export VM to OVA / OVF",
          "href": "/docs/utils/export-vm"
        },
        {
          "label": "Import VM from OVA / OVF",
          "href": "/docs/utils/import-vm"
        }
      ]
    },
    {
      "term": "OVMF",
      "aliases": [
        "UEFI firmware",
        "Open Virtual Machine Firmware"
      ],
      "category": "Virtualization",
      "definitionRich": "UEFI firmware for VMs, selected with <code>qm set &lt;vmid&gt; -bios ovmf</code>. Used for UEFI guests, including Windows 11 and Secure Boot configurations. An <code>efidisk0</code> stores persistent EFI variables; many other guests can still use legacy BIOS.",
      "seeAlso": [
        {
          "label": "Add GPU to VM (Passthrough)",
          "href": "/docs/hardware/gpu-vm-passthrough"
        }
      ]
    },
    {
      "term": "PBS",
      "aliases": [
        "Proxmox Backup Server"
      ],
      "category": "Proxmox",
      "definitionRich": "Separate Proxmox backup product providing incremental transfers, deduplication and optional client-side encryption for VM and CT backups. It can be used as a vzdump destination; a separate backup server is preferable to keeping backups on the protected host."
    },
    {
      "term": "pct",
      "category": "Proxmox",
      "definitionRich": "CLI tool for managing LXC containers in Proxmox: <code>pct list / start / stop / shutdown / config / enter / exec / push / pull / destroy</code>.",
      "seeAlso": [
        {
          "label": "VM and CT Management",
          "href": "/docs/help-info/vm-ct-commands"
        }
      ]
    },
    {
      "term": "pmxcfs",
      "aliases": [
        "Proxmox Cluster Filesystem"
      ],
      "category": "Proxmox",
      "definitionRich": "FUSE-based virtual filesystem mounted at <code>/etc/pve/</code>. Replicates configuration changes across all cluster nodes in real time. Editing a file under <code>/etc/pve/</code> propagates automatically."
    },
    {
      "term": "pveam",
      "aliases": [
        "Proxmox VE Appliance Manager"
      ],
      "category": "Proxmox",
      "definitionRich": "CLI for managing the local catalog of CT templates. <code>pveam update</code> refreshes the index; <code>pveam available</code> lists templates; <code>pveam download &lt;storage&gt; &lt;template&gt;</code> downloads one."
    },
    {
      "term": "pveproxy",
      "category": "Proxmox",
      "definitionRich": "The HTTPS service that serves the Proxmox web UI on port 8006 and the web terminal. Restarted automatically during major upgrades — which is why ProxMenux refuses to run the PVE 8 → 9 upgrade from the web terminal."
    },
    {
      "term": "pvesm",
      "aliases": [
        "Proxmox Storage Manager"
      ],
      "category": "Proxmox",
      "definitionRich": "CLI tool for managing Proxmox storage. <code>pvesm status</code> shows all configured storages; <code>pvesm add &lt;type&gt;</code> registers new ones (NFS, Samba, iSCSI, dir, ZFS, LVM, …).",
      "seeAlso": [
        {
          "label": "Storage and Disks commands",
          "href": "/docs/help-info/storage-commands"
        }
      ]
    },
    {
      "term": "Privileged container",
      "category": "Linux",
      "definitionRich": "LXC container whose root user <em>maps to host UID 0</em>, while namespaces and other restrictions still apply. Less isolated than an unprivileged container. GPU, USB and Samba access do not universally require this mode; permissions and UID mappings matter."
    },
    {
      "term": "ProxMenux Monitor",
      "category": "ProxMenux",
      "definitionRich": "Optional web dashboard installed alongside ProxMenux. Serves real-time host stats (CPU / RAM / disk / network), VM and LXC overview, login + 2FA, on TCP port <code>8008</code>.",
      "seeAlso": [
        {
          "label": "ProxMenux Monitor",
          "href": "/docs/settings/proxmenux-monitor"
        }
      ]
    },
    {
      "term": "qcow2",
      "aliases": [
        "QEMU Copy-On-Write v2"
      ],
      "category": "Storage",
      "definitionRich": "VM disk image format commonly used on directory storage. Supports allocation on demand, snapshots and copy-on-write. Convert an image with <code>qemu-img convert -O qcow2 ...</code>."
    },
    {
      "term": "qm",
      "aliases": [
        "QEMU Manager"
      ],
      "category": "Proxmox",
      "definitionRich": "CLI tool for managing VMs in Proxmox: <code>qm list / start / stop / shutdown / config / set / destroy / importdisk / migrate</code>. Sister command of <code>pct</code> for containers.",
      "seeAlso": [
        {
          "label": "VM and CT Management",
          "href": "/docs/help-info/vm-ct-commands"
        }
      ]
    },
    {
      "term": "Q35",
      "category": "Virtualization",
      "definitionRich": "Modern QEMU machine type emulating an Intel Q35 chipset with PCIe support. Recommended over the older i440FX for VMs that need PCIe passthrough or modern guest OS support. Set with <code>qm set &lt;vmid&gt; -machine q35</code>."
    },
    {
      "term": "QEMU",
      "category": "Virtualization",
      "definitionRich": "Generic, open-source machine emulator and virtualizer. Combined with KVM in Proxmox to run VMs at near-native speed."
    },
    {
      "term": "rclone",
      "category": "Linux",
      "definitionRich": "Command-line tool supporting many cloud storage providers, including Google Drive, Dropbox, OneDrive, Mega and S3. The cloud-backup guide uses it to mount remote storage as a directory for vzdump archives.",
      "seeAlso": [
        {
          "label": "Backup to Personal Cloud",
          "href": "/guides/backup_cloud"
        }
      ]
    },
    {
      "term": "Samba / SMB / CIFS",
      "category": "Storage",
      "definitionRich": "Microsoft's file-sharing protocol family. <strong>SMB</strong> is the protocol; <strong>Samba</strong> is the open-source Linux implementation; <strong>CIFS</strong> is an older SMB dialect. Registered as Proxmox storage via <code>pvesm add cifs</code>.",
      "seeAlso": [
        {
          "label": "Storage & Share Manager",
          "href": "/docs/storage-share"
        }
      ]
    },
    {
      "term": "SeaBIOS",
      "category": "Virtualization",
      "definitionRich": "Open-source legacy BIOS implementation used by QEMU. Default firmware for new VMs unless you switch to OVMF. Suitable for older OSes and simple Linux installs that don't need UEFI."
    },
    {
      "term": "smartctl / SMART",
      "aliases": [
        "Self-Monitoring, Analysis and Reporting Technology"
      ],
      "category": "Storage",
      "definitionRich": "Built-in disk diagnostics that report drive health, error counts and self-test results. <code>smartctl</code> (from <code>smartmontools</code>) is the CLI; for NVMe drives, the <code>nvme-cli</code> package adds NVMe-specific commands.",
      "seeAlso": [
        {
          "label": "SMART Disk Health & Test",
          "href": "/docs/disk-manager/smart-disk-test"
        },
        {
          "label": "Storage commands → SMART section",
          "href": "/docs/help-info/storage-commands"
        }
      ]
    },
    {
      "term": "systemd / systemctl / journalctl",
      "category": "Linux",
      "definitionRich": "Modern init system used by Debian / Proxmox. <code>systemctl</code> manages services (start / stop / enable / status). <code>journalctl</code> reads the binary log written by <code>systemd-journald</code>."
    },
    {
      "term": "sysctl",
      "category": "Linux",
      "definitionRich": "Tool for reading and changing kernel parameters. Persistent settings are commonly placed in <code>/etc/sysctl.d/*.conf</code>; support for <code>/etc/sysctl.conf</code> depends on the loader. ProxMenux Post-Install offers a sysctl tuning profile.",
      "seeAlso": [
        {
          "label": "Post-Install: Network",
          "href": "/docs/post-install/network"
        }
      ]
    },
    {
      "term": "trixie",
      "category": "Linux",
      "definitionRich": "Codename for Debian 13, the OS base for Proxmox VE 9. Predecessor: <em>bookworm</em> (Debian 12 / PVE 8).",
      "seeAlso": [
        {
          "label": "Upgrade PVE 8 to PVE 9",
          "href": "/docs/utils/upgrade-pve8-pve9"
        }
      ]
    },
    {
      "term": "udev",
      "category": "Linux",
      "definitionRich": "Linux device manager. Reacts to hardware events and creates / removes entries under <code>/dev</code>. Custom rules in <code>/etc/udev/rules.d/</code> persistently map MAC addresses to interface names, set up NVIDIA device nodes on driver load, etc."
    },
    {
      "term": "UID / GID idmap",
      "aliases": [
        "UID shift"
      ],
      "category": "Linux",
      "definitionRich": "With the default mapping in <strong>unprivileged</strong> LXC containers, host UIDs and GIDs are shifted by <code>+100000</code>: container UID 0 maps to host UID 100000, and 1000 to 101000. Custom mappings can differ; file ownership on bind mounts must match the chosen mapping.",
      "seeAlso": [
        {
          "label": "LXC Mount Points",
          "href": "/docs/storage-share/lxc-mount-points"
        }
      ]
    },
    {
      "term": "Unprivileged container",
      "category": "Linux",
      "definitionRich": "LXC container whose root maps to an unprivileged host UID, normally 100000. This reduces host privileges while sharing its kernel. Hardware access can still be configured with suitable device permissions and mappings; privileged mode is not universally required."
    },
    {
      "term": "VFIO",
      "aliases": [
        "Virtual Function I/O"
      ],
      "category": "Virtualization",
      "definitionRich": "Linux kernel framework for safe userspace device drivers — used to bind PCIe devices to VMs for direct passthrough. Enabled by loading the <code>vfio</code>, <code>vfio_iommu_type1</code> and <code>vfio_pci</code> kernel modules, configured via <code>/etc/modprobe.d/vfio.conf</code>.",
      "seeAlso": [
        {
          "label": "Post-Install: Virtualization",
          "href": "/docs/post-install/virtualization"
        }
      ]
    },
    {
      "term": "VirtIO",
      "category": "Virtualization",
      "definitionRich": "Family of paravirtualized device drivers (network, storage, balloon, GPU) that run faster than emulated legacy hardware (e.g. e1000 NICs, IDE disks). The guest needs the matching VirtIO driver — kernel-native on Linux, separate ISO install on Windows."
    },
    {
      "term": "VLAN",
      "aliases": [
        "Virtual LAN"
      ],
      "category": "Network",
      "definitionRich": "802.1Q tags that segment one physical network into multiple logical networks. Configured per-bridge or per-NIC in <code>/etc/network/interfaces</code>."
    },
    {
      "term": "VM",
      "aliases": [
        "Virtual Machine"
      ],
      "category": "Proxmox",
      "definitionRich": "Virtual machine managed by Proxmox with QEMU/KVM, running its own guest kernel. Its numeric VMID maps to <code>/etc/pve/qemu-server/&lt;VMID&gt;.conf</code>. Usually has more overhead than LXC, with a separate kernel isolation boundary.",
      "seeAlso": [
        {
          "label": "VM and CT Management",
          "href": "/docs/help-info/vm-ct-commands"
        }
      ]
    },
    {
      "term": "vzdump",
      "category": "Proxmox",
      "definitionRich": "Proxmox backup tool for VMs and CTs. File archives are <strong>not incremental</strong>; PBS targets support incremental transfers. Jobs can configure backup mode (snapshot / suspend / stop), compression (such as zstd, gzip or lzo), retention and notifications.",
      "seeAlso": [
        {
          "label": "Backup and Restore commands",
          "href": "/docs/help-info/backup-commands"
        }
      ]
    },
    {
      "term": "ZFS",
      "aliases": [
        "Zettabyte File System"
      ],
      "category": "Storage",
      "definitionRich": "Combined filesystem and volume manager with snapshots, send/receive replication, checksums and compression. It can repair corrupted data when a valid redundant copy is available. Read caching uses RAM through <strong>ARC</strong>, whose size can be limited.",
      "seeAlso": [
        {
          "label": "ZFS Management commands",
          "href": "/docs/help-info/zfs-commands"
        }
      ]
    }
  ]
}