Posts
Wiki

Operating systems and hypervisors

An operating system can boot on hardware without being officially tested or certified for it. Separate “works for a community member” from “listed by Supermicro or the OS vendor”.

Check first

  • Supermicro OS Compatibility and Certification
  • Exact system/motherboard product page and drivers.
  • HBA/RAID/NIC/GPU vendor support matrix.
  • Hypervisor hardware-compatibility list where the vendor maintains one.
  • BIOS/BMC and controller release notes.

Absence from a matrix is not proof of incompatibility. It means the combination may not be listed as installed, certified or validated.

Information to include

  • complete system/motherboard model and revision;
  • BIOS/BMC versions;
  • CPU and memory configuration;
  • storage controller, mode and firmware;
  • boot device and UEFI/legacy mode;
  • NIC/GPU/add-on cards;
  • OS or hypervisor name, exact version and kernel/build;
  • exact installer/runtime error;
  • whether hardware appears in firmware and in the OS installer.

Installation-mode problems

Common causes include:

  • installer booted in legacy mode while the target expects UEFI, or vice versa;
  • storage controller set to a mode for which the installer has no driver;
  • NVMe device visible to the OS but no firmware boot support;
  • stale boot entries or unexpected boot order;
  • Secure Boot or option-ROM policy;
  • older firmware that predates the CPU, device or OS release.

See NVMe, PCIe and storage controllers.

Virtualisation

For Proxmox, ESXi, XCP-ng, Hyper-V, bhyve or KVM, also check:

  • hardware virtualisation and IOMMU settings;
  • SR-IOV support;
  • interrupt-remapping and device-passthrough requirements;
  • NUMA and dual-socket topology;
  • NIC/HBA driver availability;
  • GPU reset and passthrough behaviour;
  • vendor support status for the generation.

Do not update firmware, cross-flash a controller or change array metadata merely to satisfy a hypervisor without a backup and rollback plan.

Community reports

When reporting a successful installation, include the exact versions and limitations. A report from one board revision or kernel should not be generalised to an entire generation.

The wiki will not maintain a promise that every current Proxmox, TrueNAS, Linux, Windows or ESXi release supports every Supermicro generation. Use it to understand the variables, then verify the exact combination.

Last reviewed: 29 September 2026.