| | |

Stuck on vSphere 7 or 8? How to get to VCF 9.1 on your EXISTING Servers (No Hardware Refresh Required!)

If you have been navigating infrastructure lifecycles lately, you know the absolute headache of the current supply chain. 🤕 Hardware shortages are very real, shipping delays are the norm, and age is rapidly catching up to your legacy silicon.

Up until February of this year, VMware Cloud Foundation (VCF) was fully prepared to leave your aging Intel 1st and 2nd Gen Xeons behind. But because of those ongoing hardware constraints, executive leadership made a massive, pragmatic call. 📞

We didn’t draw a line in the sand—we ERASED the line in the sand. 🏖️

We made the executive decision to give customers a lifeline and allow support for this older hardware so you don’t get stranded while waiting on delayed server shipments. And before you ask “Why VCF 9.1?” listen, VCF 8.0 and 9.0 are slated for End of Support in 2027. Upgrading to VCF 9.1 is the strategic target because it gives you breathing room all the way until 2028. 😌

But getting to 9.1 on older hardware? That requires understanding exactly how this executive lifeline works, specifically when it comes to the heavy confusion surrounding Skylake and Cascade Lake processors. Let’s dig in. 👇


🏗️ THE SILICON REALITY: CASCADE LAKE (2nd Gen Xeon)

Cascade Lake includes the Intel Xeon Bronze 3200, Silver 4200, Gold 5200, Gold 6200, Platinum 8200, and Platinum 9200 series.

In VCF 9.1, these are officially Deprecated. When you run the ESXi 9.x installer, you’re going to get a big warning… but you CAN still click “Continue.”

  • The RPQ Reality: Because Cascade Lake is merely Deprecated, you generally do NOT need a VMware RPQ (Request for Product Qualification) to run it.
  • The Dell Exception: There is one weird catch. If you are running Cascade Lake on Dell hardware, you DO have to file a Dell-specific RPQ. For other OEMs, just check the Broadcom Compatibility Guide (BCG).
  • The Future: Make no mistake, Cascade Lake is on the chopping block for the next major iteration—think VCF 10.x. 🪓

🛑 THE SKYLAKE SITUATION: STOP, LOOK, AND READ CLOSELY!

Skylake (1st Gen Xeon) includes the Intel Xeon Bronze 3100, Silver 4100, Gold 5100, Gold 6100, and Platinum 8100 series.

In VCF 9.1, these are officially Discontinued. There is NO “Continue” button on the installer. It is a hard stop out of the box. 🚫

Why? Because Skylake was hit hard by the Spectre and Meltdown vulnerabilities and relies entirely on software mitigations that tank performance. Even with the erased line, Broadcom has to enforce a security boundary so you don’t have to think about underlying silicon vulnerabilities causing data loss.

Because of the massive confusion here, let’s break down exactly what you CAN and CANNOT do with Skylake in VCF 9.1:

  • CAN Use the Mechanical Bypass: You CAN force the ESXi installer to ignore the hard stop. By interrupting the ESXi boot process (hitting Shift+O) and appending the boot flag allowLegacyCPU=true, you will push through the install.
  • CANNOT Call That “Supported”: You CANNOT just throw that flag in production and expect Broadcom Global Support Services (GSS) to help you when things break. The boot flag is a mechanical bypass; it does NOT grant you administrative support.
  • CAN Get Software Support via RPQ: You CAN file an RPQ (now often called a TQ – Technical Qualification) to get official “Software Only” support for your Skylake hosts, buying you up to 12 months for a hardware refresh due to supply constraints.

🔌 THE MISSING LINK & OS GOTCHAS: IT’S NOT JUST ABOUT THE CPU!

It is absolute crazy town to hyper-focus on your CPU and completely forget the rest of the chassis! 🤯 Erasing the line for CPUs doesn’t give you a free pass on your network cards or storage controllers.

You MUST validate every I/O component in that chassis against the BCG. A supported CPU means nothing if your 10Gb NICs or HBAs are blind to the hypervisor.

Furthermore, you CANNOT expect modern operating systems to play nice. Microsoft Windows Server 2025 has officially dropped support for Intel Skylake CPUs. You MUST align your hardware reality with your guest OS reality! 🖥️


🗺️ TAKING THE LIFELINE: THE OEM GUIDANCE & RPQ JOURNEY

Okay, so you have a cluster of Skylake servers, your I/O components check out on the BCG, but your hardware refresh is delayed. How do you survive and get to VCF 9.1 fully supported today? You need that RPQ. 📝

Here is exactly how you steer your TAM (Technical Account Manager) or SE (Sales Engineer) to get this done:

  • 1️⃣ Call your TAM/SE: Tell them you need an RPQ for VCF 9.1 “Software Only” support on your legacy CPUs to buy you time for a hardware refresh due to supply constraints.
  • 2️⃣ Secure the OEM Pre-Condition: The absolute biggest hurdle for a VMware RPQ approval is your OEM. VMware will only approve software support IF your server vendor agrees to continue supporting the aging hardware.
  • 3️⃣ Do the Heavy Lifting: Tell your TAM/SE, “I have already checked with my OEM. They have agreed to continue providing support for the I/O, the NICs, and most importantly, the BIOS and microcode updates.” That OEM confirmation is your entire journey.
  • 4️⃣ Engage Professional Services: Once your existing hardware is confirmed and the RPQ is approved, do not go it alone. Engage Broadcom Professional Services or a certified delivery partner to architect and execute the actual upgrade. 🤝

💡 The Architect’s Takeaway: VCF 9.1 is your strategic bridge to 2028, and leadership intentionally erased the line in the sand to help you get there despite supply chain chaos. But you have to respect the hardware boundaries. Check your NICs, align your guest OS, get your OEMs in line, leverage your TAMs, file the RPQ to buy your refresh time, and let the software do what it was designed to do!


📚 RECOMMENDED RESOURCES & FURTHER READING

For those of you ready to dive deeper into the architectural compatibility requirements for VCF 9.1, check out these official resources:

Have questions about navigating the RPQ process for your specific hardware, or planning your path to VCF 9.1? Drop them in the comments or message me—we’re all navigating this together. 🤝 Like, repost, or tag someone planning their next hardware refresh or VCF upgrade.

This article is part of the Architect’s Edge Insights series designed to cut through confusion and deliver clarity on VMware Cloud Foundation. Stay tuned for upcoming posts as we continue to simplify VCF adoption, operations, and optimization. Read the original article on LinkedIn.

#VMware #VCF9 #VMwareCloudFoundation #CloudArchitecture #vSphere #IntelXeon #HardwareRefresh #EnterpriseArchitecture #PlatformEngineering #ITOps #Broadcom #SDDC #PrivateCloud #ArchitectsEdge #Datacenter #Infrastructure #vExpert

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *