Hardware compatibility list

Also known as: HCL

On this page 7

A hardware compatibility list (HCL) is a vendor-maintained catalog of computers, components and peripherals that have been tested and certified to work with a specific operating system or platform release. In OS compatibility, the HCL answers a narrow but decisive question: will this exact processor, storage controller, network adapter or graphics card run correctly and remain supported under this version of the system?

Hardware compatibility lists are most important where failure is expensive. Server operating systems, hypervisors, enterprise Linux distributions and storage platforms rely on them to define the boundary of vendor support, while desktop users meet the same idea in the form of minimum system requirements and driver availability.

How a hardware compatibility list is built

An HCL is built through a formal certification process in which the hardware maker, the OS vendor or both run a defined test suite against a specific device and firmware combination. A device passes only when it completes stress, stability and driver tests without errors, and the listing then records the exact model, firmware revision and driver version that were validated.

The entry is therefore narrower than many readers assume. A listing usually covers one OS release or update level, one driver version and a defined configuration, such as a particular RAID mode or maximum memory size. Changing any of those variables can move a system outside the certified scope, even when the hardware still appears to work.

The following table shows the typical elements of a single HCL entry and why each one matters.

FieldExample contentWhy it matters
Device modelSpecific controller or server modelIdentifies the exact tested hardware
Firmware versionBIOS, UEFI or controller firmware levelFirmware bugs can break stability
Driver versionInbox or vendor driver buildUntested drivers may cause crashes
OS releaseMajor version and update levelSupport is tied to specific releases
Configuration notesRAID mode, memory limits, slot rulesDefines the supported operating envelope
Certification dateDate the test completedShows how current the validation is
Typical fields in a hardware compatibility list entry

Types of hardware compatibility lists

HCLs differ mainly in who maintains them and how strict the certification is. An enterprise hypervisor vendor may refuse support for unlisted hardware, whereas a community-run Linux list only records user-reported results without any guarantee.

The table below compares the main categories found across operating systems and platforms.

List typeMaintained byStrength of guaranteeTypical audience
Vendor certification listOS or hypervisor vendorStrong, tied to support contractsData center teams
Hardware maker certificationServer or component makerStrong for listed OS versionsSystem integrators
Driver signing programOS vendor with hardware partnersModerate, focused on driver qualityDesktop and laptop users
Community databaseUsers and volunteersWeak, based on reportsEnthusiasts and hobbyists
Storage interoperability matrixStorage or backup vendorStrong for exact combinationsStorage administrators
Main categories of hardware compatibility lists

An HCL is distinct from other OS compatibility tools because it addresses hardware certification, not software behavior. System requirements define a minimum baseline, driver compatibility concerns whether a working driver exists, and a compatibility layer such as Wine deals with running foreign application code.

ConceptQuestion it answersScope
Hardware compatibility listIs this exact device certified?Specific models and versions
System requirementsIs the machine powerful enough?Minimum CPU, memory and storage
Driver compatibilityDoes a working driver exist?Driver model and OS version
Compatibility layerCan foreign software run here?Application binaries and APIs
EmulationCan another platform be imitated?Entire instruction sets or devices
How an HCL differs from neighboring concepts

The distinction matters in practice. A server can easily exceed the system requirements of an operating system and still be absent from the HCL, which typically means the vendor will not accept support cases for problems on that hardware.

Using a hardware compatibility list in practice

Administrators consult the HCL before purchasing hardware, before upgrading an operating system and before changing firmware. The most reliable workflow is to search for the exact model, confirm the target OS release and then compare the listed firmware and driver versions with what is actually installed.

The decision table below summarizes common situations and the recommended approach.

SituationRecommended actionReason
New server purchaseBuy only listed models and optionsKeeps the full stack supportable
Planned OS upgradeCheck the HCL for the new releaseOlder hardware is often dropped
Firmware update availableMatch the version named on the HCLNewer firmware may be uncertified
Device missing from the listAsk the vendor or test in a labAbsence is not proof of failure
Home desktop buildCheck driver availability and requirementsFormal HCLs rarely cover consumer parts
Decision table for common HCL situations
  • Record the exact firmware and driver versions at deployment so later audits are possible.
  • Recheck the list after every major OS update, because certification does not carry forward automatically.
  • Treat component substitutions, such as a different network card, as a new compatibility check.

Limitations and common misconceptions

The most common misconception is that unlisted hardware will not work. In reality, many unlisted devices run without problems; the list only records what has been formally tested, and vendors often skip certification for older, low-volume or consumer models because testing is costly and time-consuming.

The opposite error is equally risky. A listed device can still fail if it runs uncertified firmware, an unsupported driver or a configuration outside the documented limits. HCLs also age quickly: an entry certified for one release may be deprecated in the next, which is a frequent cause of failed upgrades on older servers.

  • Listing is version-specific, so a model certified for one release is not automatically certified for its successor.
  • Absence is not incompatibility, but it usually means the vendor will not support the configuration.
  • Partial certification is common: a server may be listed while one of its optional controllers is not.

A non-technical view

A hardware compatibility list works like the list of approved replacement parts for a car. The parts on the list have been checked by the manufacturer, so a mechanic knows they will fit and that the warranty still applies. A part that is not on the list might work perfectly, but nobody has promised that it will.

For computers, the operating system maker publishes this kind of list for processors, disks, network cards and whole machines. The key idea is simple: listed hardware comes with a promise of support, while unlisted hardware is used at your own risk.

A concrete example

An IT team at a mid-sized hospital plans to move twelve virtualization hosts from one hypervisor release to the next. Before scheduling the upgrade, an administrator checks the vendor HCL and finds that the servers are still listed, but their storage controller is certified only with a newer firmware version than the one installed. The network adapters are listed without restrictions.

The team first updates the controller firmware on a single test host, runs a week of load tests and then rolls the change out to the remaining hosts. Only after every host matches the certified firmware and driver combination do they perform the hypervisor upgrade. The result is a fully supported cluster and a clean upgrade with no storage errors, whereas skipping the check could have left the hospital with an unsupported configuration during a critical outage.