Executive Summary

VMware Cloud Foundation (VCF) 9.0 is designed to enable customers to modernize their cloud infrastructure, and part of that design is doing so without forcing unnecessary hardware refresh cycles. It was therefore exciting news to announce that, following data-driven reviews in pursuit of that design, the majority of servers certified for vSphere and vSAN 8.x were automatically carried forward and are supported in VCF 9.0.

This blog clarifies how VCF server hardware certification works (including for VCF 9.0), and how Broadcom’s responsibility for a supported third party hardware remains to the VCF software and not the hardware of that third party, what it means when a server is marked ”VCF Supported. Confirm w/ Vendor” in the Broadcom Compatibility Guide (BCG), and under what limited conditions a server may not be listed. In short, if your infrastructure is running on supported vSphere or vSAN 8.x hardware today, it is highly likely to be eligible for VCF 9.0.

VCF Server Certification: An Overview

VCF server certification is addressed across two complementary dimensions:

• Component Level
• Server Model Level

This model ensures platform stability, predictable operations, and clear support ownership across the ecosystem.

Component-Level Support

From the VCF perspective, server support is determined by the qualification of the constituent components that form a server platform, including:

• CPU Series/Family
• Network and I/O devices (NICs, DPUs, HBAs)
• GPUs and accelerators
• Storage controllers and device types
• Firmware and driver combinations

If these components are validated as supported under applicable certifications of a particular version of VCF (e.g. VCF 9.0), Broadcom can support the server platform from a functional and lifecycle standpoint for that version. These validated combinations are enforced to ensure consistent Day-0 through Day-2 operations.

Server Level Support

For a server to earn certification under the VCF Server Certification Program, that particular server model must go through testing against certification standards that the Broadcom engineering team established for that VCF version. Once a model passes certification, and the results are validated, Broadcom will list that server model on the the Broadcom Compatibility Guide (BCG), confirming that Broadcom support services cover that particular VCF software version running on that particular server model.. 

It’s important for customers to understand that certification of a server or a hardware doesn’t extend Broadcom’s support services to the underlying server hardware, – that remains the OEM’s responsibility. Broadcom support services apply strictly to the VCF software layer. VCF certification is therefore independent of the OEM’s hardware obligations. Your server OEM/vendor remains solely responsible for everything outside of the VCF software, including:

• Server Model and CPU Series SKU definitions, BIOS/firmware and microcode patches related to security vulnerability bundles
• OEM-supported driver stacks
• Hardware warranties and field support commitments

This clear division of responsibilities ensures you receive expert support at every layer, being Broadcom for your VCF software, and your OEM vendor for the rest of the server.

Carrying Forward vSphere and vSAN 8.x Servers into VCF 9.0

A key objective of VCF 9.0 is hardware continuity, – meaning enable customers to modernize their cloud infrastructure, and part of that design is doing so without forcing unnecessary hardware refresh cycles. VCF certification programs, including Server Certification, have historically included a process for carrying forward certifications of existing devices from one version to the next when technically justified. This causes efficiencies on all parties. OEM vendors do not need to reapply, and customers’ current hardware investments can continue delivering value if they upgrade to the newer version of VCF.

This is exactly what we are proud to have accomplished by announcing that the majority of servers certified for version 8.x were automatically carried forward and are supported in VCF 9.0. Customers get the latest capabilities while maximizing the return on their existing hardware investments. As such:

• Servers certified for vSphere and vSAN 8.x are carried forward into VCF 9.0 wherever the underlying components remain supported.
• Customers should expect continuity across major versions (VCF 9.0), avoiding unnecessary disruption or forced refresh.
• Carried Forward into VCF 9.0 BCG listings now total 3,148 server models

This approach enables customers to upgrade the software stack while preserving existing infrastructure investments.

Broadcom Compatibility Guide: The Source of Truth

The Broadcom Compatibility Guide (BCG) remains the authoritative reference for VCF 9.0 hardware support.

Systems / Servers listings fall into one of three categories:

• VCF Supported: Supported by both Broadcom and the OEM. Default listing in BCG
• VCF Supported. Confirm w/ Vendor: Supported by Broadcom for the VCF software running on the certified hardware or server, but OEM confirmation required to confirm if they support their server hardware either as a standard practice or an exception (such as an RPQ (Request for Product Qualification)).
• Not listed: One or more core components have reached end-of-service life and can no longer be supported

Each status reflects component lifecycle and supportability considerations.

Understanding “VCF Supported. Confirm w/Vendor” Server Listings

A ”VCF Supported. Confirm w/Vendor” designation indicates that:

• VCF 9.x support for the CPU Series/Family is current.
• If the System / Server OEM did not submit for certification, that System / Server may be marked with the keyword “VCF Supported. Confirm w/Vendor”.
• No further system level driver enhancements.
• Best effort to provide fixes and/or workarounds for VCF Software Only level of support.

This scenario commonly arises when certain components — such as CPU Series/Families such as Intel Cascade Lake or Intel Skylake — are at end-of-sale but not end-of-service. While silicon vendors may continue to provide firmware/microcode security vulnerability updates, some OEMs require additional validation or approvals before extending full certification.

In these cases, customers can engage the server OEM/vendor to confirm if they support their server hardware either as a standard practice or an exception (such as an RPQ). From the VCF perspective of its support for VCF Software Components running on those servers, no additional action is required.

What if a Server Is Not Listed for VCF 9.0

In limited cases, a server previously certified for 8.x may not appear in the VCF 9.0 BCG listing.

This occurs when a core component of server is fully end-of-service life (EOSL), meaning:

• No security or microcode updates are available
• No supported or signed drivers exist
• Continued operation presents unacceptable security or operational risk

Examples include older CPU Series/Families such as Intel Haswell or Broadwell. In these scenarios, exclusion is driven by industry lifecycle and security realities rather than platform policy.

Hardware Equivalency

VCF works with OEM/vendor partners and applies equivalency rules when listing compatible hardware.

For example, configurations using:

• Equivalent CPU stepping
• Functionally identical I/O devices
• Validated firmware and driver combinations

may qualify for VCF 9.0 even if the exact SKU is not explicitly listed. These equivalencies are documented in the BCG to help customers maximize reuse of existing platforms.

vSAN Compatibility and Simplified Requirements

Most servers that are certified for vSphere 8.x are also certified for vSAN.

With VCF 9.0:

• vSAN hardware requirements are simplified into three profiles: Small, Medium, and Large
• Hardware requirements for both vSAN HCI and vSAN storage clusters are reduced by nearly 50%
• Many customers can enable vSAN by adding a small number of cost-effective NVMe devices, without changing server platforms

This significantly lowers the barrier to adopting vSAN as part of a VCF 9.0 upgrade.

Certification Lifecycle and Versioning

The certification process remains consistent:

• No recertification is required for minor releases
• Certification updates are triggered for major versions only

This ensures stability and predictability across the lifecycle of the platform.

To Summarize: What This Means for Customers

Customers planning to upgrade to VCF 9.0 should:

1. Validate server configurations in the BCG
2. Engage OEMs for validation of their support, or issuance of an exception under RPQs, if a server is “VCF Supported. Confirm w/Vendor”
3. Review component lifecycle if a server is not listed
4. Consider vSAN enablement through incremental NVMe additions

Designed to Minimize Hardware Refresh

VCF 9.0 is explicitly designed to:

• Preserve existing hardware investments
• Carry forward supported platforms across major versions
• Simplify storage requirements
• Reduce operational and upgrade risk

Unless constrained by component end-of-service life, customers should expect a smooth transition to VCF 9.0 using their existing server infrastructure.

Frequently Asked Questions

Do I need to refresh hardware to upgrade to VCF 9.0?
No. Most customers can upgrade using servers already certified for vSphere or vSAN 8.x.

What does “VCF Supported. Confirm w/ Vendor” mean in the BCG for VCF 9.0?
VCF 9.0 supports the server configuration, but OEM validation is required to confirm if they support their hardware either as a standard practice or an exception (such as via an RPQ process).

Why is my 8.x server missing from the 9.0 list?
Only servers with core components that are fully EOSL are excluded.

Intel Skylake CPU Series is no longer listed on the BCG. Can this still be supported for VCF 9.0?
Yes, but subject to a Broadcom-VMware RPQ filing. 

Since the CPU Series is no longer supported for VCF 9.0, filing a Broadcom-VMware RPQ will be required, and approvals are granted based on appropriate business justifications. In addition, customers are also encouraged to reach out to their OEM vendors to obtain hardware side support. By default, the Broadcom-VMware RPQ, upon approval only provides “VCF Software Only” support, and the customer must secure their OEM vendors agreement to support their ageing HW, firmware and/or microcode patches.

Are there any Broadcom-VMware KB articles which can provide more in-depth information?
Yes. Here is a list of relevant KB articles:

• CPU Series Deprecation and Discontinuation in ESX / VCF Releases (KB article 318697) 
• Systems / Servers Deprecation in ESX 9.0 and implications for support (KB article 428874)
• Deprecated devices in ESX 9.0 and implications for support (KB article 391170)

Can I adopt vSAN without new servers?
Yes. In many cases, adding a small number of NVMe devices is sufficient. To learn more please read this vSAN FAQ