Most buying mistakes in server hardware come from one assumption: if it fits, it works. A memory module that clicks into the slot, a drive that slides into the bay, or a network card that seats in the PCIe slot can still fail to work properly. Sometimes it will not be detected at all. Sometimes it works for a week and then causes random errors.
Compatibility lists exist to prevent this. They are not marketing. They are test records. This guide explains what they are, where to find them, and how to use them before you spend money.
What Is a QVL?
QVL stands for Qualified Vendor List. It is a list published by a motherboard or server maker showing which parts they have tested and confirmed work with a specific board or system.
You will most often see QVLs for memory, but they can also cover storage drives, CPUs and add-in cards. A typical memory QVL entry shows the module brand, part number, capacity, speed, rank, and which chips are on the module.
A part on the QVL has been tested on that exact board, usually at the speeds and populations listed. A part that is not on the QVL may still work, but nobody has confirmed it.
What Is an HCL?
HCL stands for Hardware Compatibility List. This usually comes from the software side. Operating system and hypervisor vendors publish lists of hardware they have tested or certified for their products.
Examples include the VMware Compatibility Guide, the Windows Server Catalog from Microsoft, and the certified hardware lists from Red Hat, SUSE and Ubuntu.
The HCL answers a different question from the QVL. The QVL asks whether the part works with this server. The HCL asks whether the part works with this operating system or hypervisor, and whether the vendor will support you if something breaks.
QVL vs HCL at a Glance
| QVL | HCL | |
|---|---|---|
| Published by | Server or motherboard maker | OS or hypervisor vendor |
| Question it answers | Does this part work with this server? | Does this part work with this software? |
| Typical parts covered | Memory, drives, CPUs, add-in cards | Servers, storage controllers, network cards, drives |
| Based on | Testing on specific boards | Testing or certification for a software version |
| Matters most for | Memory and storage purchases | Virtualization and supported production systems |
| If a part is missing | Not tested, may still work | Not certified, support may be refused |
You need both in many cases. A server can accept a network card (QVL), but if your hypervisor does not list that card, driver issues or support refusals can follow.
Why Compatibility Lists Matter
Servers are stricter than desktop PCs. They use registered or load-reduced memory, ECC error correction, firmware checks and hardware monitoring. Server makers often validate parts and tune firmware around them.
Here is what can go wrong with a part that is not on the list.
- The server does not detect the part at all.
- The part runs at a lower speed than advertised.
- The server shows warnings at boot or in the management controller.
- Random errors appear under load, which are hard to trace.
- Fans spin faster or the system refuses to boot with unsupported drives or cards.
- A vendor support case gets rejected because the part was not qualified.
Memory is the most common problem area. Two modules with the same capacity and speed can use different chips and different registers. Firmware may handle one well and the other poorly.
Where to Find the Lists
Start with the maker of the server or board, then check the software side.
| Source | What you find |
|---|---|
| Server maker websites (Dell, HPE, Lenovo, Supermicro, Cisco) | Memory, drive, CPU and card compatibility for each model |
| Motherboard maker support pages | Memory QVL as a PDF or web table for each board |
| VMware Compatibility Guide | Certified servers, storage controllers and network cards for each ESXi version |
| Windows Server Catalog | Microsoft certified hardware |
| Red Hat, SUSE, Ubuntu certified hardware pages | Tested servers and components |
| Part maker pages (Samsung, Micron, SK hynix, Intel, Broadcom) | Platform compatibility notes for their parts |
Many server makers also publish memory population guides. These tell you which slots to fill and which speeds are possible with each CPU. Read this along with the QVL.
A memory QVL is usually a table with several columns. Here is what to check.
| Column | What to check |
|---|---|
| Part number | Match the full part number, not just the brand and capacity |
| Capacity | Matches what you plan to install per slot |
| Speed | The speed the module is rated for, which may be higher than the system will run |
| Type | RDIMM, LRDIMM or UDIMM, which must match what the server supports |
| Rank | Single, dual or quad rank, which affects how many modules the board can handle |
| Tested speed | Some lists show the speed achieved at 1 or 2 modules per channel |
| DIMMs per channel | Shows what population was tested |
Pay attention to the tested speed. A DDR5 module rated for one speed may run slower when two modules share a channel, or when a certain CPU is installed. The QVL tells you what was confirmed, not just what the module is rated for.
The Part Number Trap
Part numbers matter more than brand names. Two Samsung modules can look alike and still be different products. The difference may be speed, rank, die revision or the target platform.
Many modules also have a manufacturer part number and a separate reseller or OEM part number. The QVL may list one or the other. When in doubt, search the list by the manufacturer part number printed on the module label.
If a seller cannot tell you the exact part number, that is a warning sign. Compatibility cannot be checked without it.
What If the Part Is Not on the List?
Not being listed does not mean it will fail. Lists lag behind new parts, and makers cannot test everything. But you take on the risk.
Here is a practical way to handle it.
- Look for a similar part from the same manufacturer, with the same chip type, speed and rank, that is on the list.
- Check whether the part maker lists your platform as supported.
- Ask the seller whether it has been used in the same server model, and ask for a return policy.
- Buy one unit first and test it before buying a full set.
- Keep your firmware updated, since newer BIOS and BMC versions often add support for more parts.
For production servers with vendor support contracts, stay with listed parts. An unlisted part can give the vendor a reason to refuse help.
Common Mistakes
| Mistake | What happens | Fix |
|---|---|---|
| Matching only capacity and speed | Part is unrecognized or unstable | Match the full part number to the list |
| Checking only the motherboard, not the CPU generation | Speed drops or modules are not supported | Check CPU support in the same document |
| Mixing different memory parts in one server | Lower speed or boot errors | Use identical modules where possible |
| Ignoring the HCL for virtualization | Driver issues or no vendor support | Check the hypervisor guide for cards and controllers |
| Reading an old list | Newer firmware may change support | Check the list version and update firmware |
| Assuming OEM and retail parts are the same | Branded servers may lock certain parts | Use parts listed for your exact server brand |
| Buying a full order before testing | Expensive returns if it fails | Test one unit first |
A Simple Checklist for Buying
Before you order any server part, go through these steps.
- Write down the exact server or board model and the CPU generation.
- Find the maker's compatibility list for that model.
- Search the list for the exact part number.
- Check the software side if you run VMware, Windows Server or Linux with vendor support.
- Confirm the speed the system will actually run at.
- Ask the seller about returns if the part is unlisted.
- Update firmware before you install.
This takes a few minutes and avoids most of the failed upgrades people report.
When Compatibility Lists Are Not Enough
Lists are a starting point. They do not cover every setup. A part may be listed but still behave badly in a specific configuration, such as a full memory population with a high-core CPU.
After installing, verify the result. Check that the BIOS shows the right capacity and speed, review the management controller logs for errors, and run a memory test before putting the server into production. Catching problems early is much cheaper than finding them during a busy day.
FAQs
What does QVL stand for?
Qualified Vendor List. It is a list of parts tested by a server or motherboard maker to work with a specific board or system.
What does HCL stand for?
Hardware Compatibility List. It is published by software vendors such as VMware, Microsoft and Red Hat to show hardware tested for their operating systems or hypervisors.
Will a part that is not on the QVL work?
It might. Many parts work without being listed, but there is no confirmation. For production servers, stick with listed parts when you can.
Is the QVL the same as the HCL?
No. The QVL covers hardware compatibility with a specific server or board. The HCL covers compatibility with an operating system or hypervisor.
Where do I find the QVL for my server?
On the support or product page of the server or motherboard maker. Search for your exact model and look for memory or component compatibility documents.
Do I need to match the exact part number?
Yes, when possible. Capacity and speed alone are not enough. Different part numbers can use different chips or have different firmware behavior.
Can I mix memory brands in one server?
It can work, but it is not recommended. Mixed modules may run at the lowest common speed or cause errors. Identical modules are safer.
Does using unlisted parts void the warranty?
Not always, but the vendor may refuse support if the issue seems related to an unqualified part. Check your support contract terms before you buy.
How often are compatibility lists updated?
It varies by maker. New parts and firmware versions are added over time, so check that you are reading the latest version.