Intel Skylake and ESX 9: Skylake-SP Supported in Deprecated Mode for VCF 9.x, Not Beyond

Is Intel Skylake supported in ESX 9? Skylake-SP runs in Deprecated mode for all VCF 9.x (KB 428874), not beyond. Skylake-W stays discontinued.

Illustration of an Intel Skylake server CPU reaching end of support in vSphere

Short answer: Yes, with limits. Broadcom KB 428874 was updated on 18 September 2026. Intel Skylake-SP (Xeon Scalable 1st generation: Platinum 8100, Gold 6100/5100, Silver 4100, Bronze 3100) is now supported in Deprecated mode for all of VCF 9.x, including 9.0 GA. Support depends on BCG listing and OEM hardware support. It will not be extended beyond 9.x. Skylake-W (Xeon W-2100) remains discontinued.

This post covers Skylake specifically. For the general installer warning (“may not be supported in future ESXi releases”) and the full CPU tables, see KB 82794 explained.

Intel Skylake ESXi 9 support at a glance

Skylake variantBCG CPU seriesCPU Info / CPUIDKB 318697 status for 9.x
Skylake-SPXeon Platinum 8100, Gold 6100/5100, Silver 4100, Bronze 31006.55.4 / 0x00050654See KB 428874: Deprecated mode for VCF 9.x
Skylake-DXeon D-21006.55.4 / 0x00050654See KB 428874
Skylake-SXeon E3-1200-v5, E3-1500-v56.5E.3 / 0x000506E3See KB 428874
Skylake-WXeon W-21006.55.4 / 0x00050654Discontinued

Note: the text of KB 428874 names only Skylake-SP explicitly. KB 318697 points the Skylake-D and Skylake-S rows to it as well. If you run Xeon D-2100 or E3 v5 systems, check the BCG listing for your exact server model. The other VCF 9 hardware checks (I/O devices, deprecated drivers, vSAN ESA) are in How to check VCF 9 hardware compatibility.

How Skylake support changed from vSphere 8 to VCF 9.x

  • vSphere 8.x: Skylake was on the deprecation list. The ESXi 8 installer warned that the CPU may not be supported in future releases, and installation continued. The original version of this post (October 2024) covered that stage.
  • VCF 9.0 GA: Skylake-SP was discontinued and not listed in the BCG for 9.0. In February 2026, Broadcom’s VCF blog still said Skylake needed an RPQ, with “VCF Software Only” support on approval.
  • KB 428874, 4 July 2026: the KB added Skylake-SP support for VCF 9.1.x.
  • KB 428874, 18 September 2026: support was expanded to VCF 9.x, including 9.0 GA. No TQ/RPQ is required for certain OEM server models marked “VCF Supported. Confirm w/ Vendor”.

Advice from older posts and forums, such as “Skylake does not install on ESX 9” or “file an RPQ”, may be out of date. Check the KB’s update date before you decide.

What Deprecated mode means for an Intel Skylake server

  • Deprecated means still supported. Per KB 318697, the CPU series is supported through the life of the VCF release, its updates and patches, or until End of General Support.
  • The OEM must list the server model in the Broadcom Compatibility Guide. KB 428874 links a BCG search for Skylake systems marked “VCF Supported. Confirm w/Vendor” on ESXi 9.0 and 9.1.
  • “VCF Supported. Confirm w/Vendor” means no further system-level driver enhancements and best-effort fixes or workarounds for the VCF software only.
  • Hardware, BIOS, firmware and microcode support comes from the server OEM and Intel under your contract with them. If you have no such support, you carry the risk.
  • vSAN OSA and ESA ReadyNodes with Skylake-SP are also in Deprecated mode and still supported.

Installing or upgrading ESX 9 on Skylake-SP

KB 428874 says the specific install and upgrade paths for VCF 9.x are described in its attached document, ESX_9.x_Install_Upgrade_using_OVERRIDE_on_Skylake_CPU_based_Servers-v1.3-09182026.pdf. Download it from the KB page and follow it for your path (fresh install, ESX upgrade, or a VCF-managed upgrade). I have not reproduced its steps here because they are versioned and still changing. This is Broadcom’s supported procedure. Don’t confuse it with the unsupported homelab boot option allowLegacyCPU=true.

Is it Skylake or Cascade Lake? Check the stepping

Skylake-SP and Cascade Lake-SP use the same family and model (hex 6.55, decimal model 85). Only the stepping tells them apart: 4 is Skylake-SP, and 6 or 7 is Cascade Lake. Cascade Lake is Deprecated in 9.x and listed as Discontinued for the next major release.

esxcli hardware cpu list
# look at: Brand, Family, Model, Stepping (decimal values)
# Family 6, Model 85, Stepping 4    -> Skylake-SP (6.55.4)
# Family 6, Model 85, Stepping 6/7  -> Cascade Lake (6.55.6 / 6.55.7)

What happens after 9.x

KB 428874 is explicit: Skylake-SP support will not be extended to VCF releases beyond 9.x. In KB 318697’s definitions, a “future major release” is the release after the 9.x series. The same table lists Cascade Lake, AMD EPYC 7001 (Naples) and 7002 (Rome), Coffee Lake Xeon E-2100/E-2200 and Atom C3000 as discontinued in that release. For planning:

  1. Inventory hosts by CPU stepping, not only by server model.
  2. Treat Skylake-SP hosts as “last stop: VCF 9.x” and track the 9.x End of General Support date in the Broadcom Product Lifecycle Matrix.
  3. Confirm OEM hardware and firmware support for the remaining lifetime. KB 428874 puts this responsibility on the OEM and Intel.
  4. Plan the refresh so the cluster does not block the next major upgrade. Avoid mixing in new Cascade Lake purchases, which hit the same wall.

Sources

Related on vdan.cz

vSphere Client Instability After vCenter 8.0.3.00200 (8.0 U3b): Moved

This note moved. The full article covers the vCenter 8.0 U3b idle session bug, KB 377734, the 8.0 U3c fix and vCenter session timeout settings.

This note has been merged into a single, updated article.

After upgrading to vCenter Server 8.0.3.00200 (8.0 Update 3b), the vSphere Client could become unresponsive after a long idle period. The cause was a changed Tomcat default (RECYCLE_FACADES), described in Broadcom KB 377734. It is fixed in vCenter 8.0 Update 3c and later.

The full article covers the symptoms, the KB workaround, the fixed builds and how to set the vSphere Client session timeout in vCenter 8.0 and 9.x:

vCenter 8 Session Timeout Settings and the 8.0 U3b vSphere Client Idle Session Bug (Fixed in 8.0 U3c)

VMSA-2024-0019: Critical VMware vCenter Server Vulnerabilities (CVE-2024-38812, CVE-2024-38813) Addressed

VMSA-2024-0019 covers vCenter heap-overflow CVE-2024-38812 and privilege escalation CVE-2024-38813. Affected versions and fixed builds (8.0 U3d, 7.0 U3t).

VMware has released an important security advisory, VMSA-2024-0019, detailing updates for VMware vCenter Server that address two significant vulnerabilities: a heap-overflow vulnerability (CVE-2024-38812) and a privilege escalation vulnerability (CVE-2024-38813). Both of these vulnerabilities could have severe implications if exploited, making it crucial for administrators to apply the necessary patches promptly.

Heap-Overflow Vulnerability (CVE-2024-38812)

Description: The first vulnerability, identified as CVE-2024-38812, is a heap-overflow vulnerability found in the vCenter Server’s implementation of the DCERPC protocol. This issue has been classified by VMware as Critical, with a maximum CVSSv3 base score of 9.8, indicating the potential for severe impact.

Known Attack Vectors: A malicious actor with network access to the vCenter Server can exploit this vulnerability by sending a specially crafted network packet. Successful exploitation could lead to remote code execution (RCE), allowing the attacker to execute arbitrary code on the vCenter Server with potentially full system privileges. This level of access could be used to disrupt services, exfiltrate sensitive data, or further compromise the virtual environment.

Privilege Escalation Vulnerability (CVE-2024-38813)

Description: The second vulnerability, CVE-2024-38813, is a privilege escalation flaw within the vCenter Server. VMware has rated this issue as Important, with a CVSSv3 base score of 7.5. While not as severe as the heap-overflow vulnerability, it still poses a significant risk.

Known Attack Vectors: An attacker with network access to the vCenter Server can exploit this vulnerability by sending a specially crafted network packet. If successful, the attacker could escalate their privileges to root, gaining full administrative control over the vCenter Server. This level of access could enable the attacker to make unauthorized changes, access sensitive information, or disrupt the entire virtual infrastructure.

More info VMSA-2024-0019:VMware vCenter Server updates address heap-overflow and privilege escalation vulnerabilities (CVE-2024-38812, CVE-2024-38813)

Tips & Tricks for deploying VMware Cloud…

Tips & Tricks for deploying VMware Cloud…

The VMware Cloud Foundation (VCF) Holodeck Toolkit has become quite popular amongst our field teams for quickly spinning up a fully self-contained VCF environment, running on just a single physical ESXi host for educational and hands on experience. Internally, we have a Holodeck Google Space […]


VMware Social Media Advocacy

What’s Included in VMware vSphere Foundation (VVF) 9.x: Components, vSAN Entitlement, Add-ons and Licensing

VMware vSphere Foundation (VVF) 9.x: the included components, the 0.25 TiB/core vSAN entitlement, paid add-ons, core counting and 9.1 licensing.

Short answer: VMware vSphere Foundation (VVF) is Broadcom’s per-core subscription for the vSphere platform. It bundles vSphere Enterprise Plus, vCenter Standard, vSphere Kubernetes Service and VCF Operations (including logs and diagnostics), plus 0.25 TiB of raw vSAN capacity per licensed core. NSX, VCF Automation and SDDC Manager-style fleet lifecycle stay in VMware Cloud Foundation. Extra vSAN capacity, SRM / Live Recovery and Avi are paid add-ons.

VVF and VCF were introduced at the end of 2023, when Broadcom replaced the long list of vSphere editions and bundles with two main offers. This article lists what VVF actually contains today. For an edition-by-edition comparison (VVF vs VCF vs the remaining vSphere 8 editions), see my vSphere 9 product line comparison.

VMware vSphere Foundation components

According to the VMware vSphere Foundation 9.1 FAQ, VVF includes:

ComponentWhat it gives you
vSphere Enterprise PlusESX hypervisor with the full feature set: DRS, HA, vMotion, Storage vMotion, distributed switch, host profiles and configuration profiles
vCenter StandardCentral management, Enhanced Linked Mode, vSphere Lifecycle Manager
vSphere Kubernetes Service (VKS)Supervisor and conformant Kubernetes clusters next to VMs (formerly Tanzu Kubernetes Grid)
VCF OperationsMonitoring, capacity, compliance; includes VCF Operations for logs and VCF Operations diagnostics (formerly Aria Operations, Aria Operations for Logs and Skyline)
vSAN0.25 TiB raw capacity per licensed VVF core
SupportBroadcom Software Maintenance Essential Support

How the vSAN entitlement works in VVF

  • Each VVF core includes 0.25 TiB of raw vSAN capacity; VCF includes 1 TiB per core (KB 313548). The total is rounded up to the nearest whole TiB.
  • Capacity is pooled across the whole VVF estate, so cores in compute-only clusters still add to the TiB you can use in vSAN clusters.
  • vSAN is optional. VVF runs fine on NFS or Fibre Channel storage.
  • There are no vSAN editions inside VVF: encryption, stretched clusters and vSAN storage clusters (formerly vSAN Max) are all included.
  • Capacity beyond the entitlement requires the vSAN add-on.

Worked example: counting VVF cores and vSAN TiB

Licensing is per physical core with a minimum of 16 cores per CPU (KB 313548). A 4-host cluster with two 12-core CPUs per host is therefore licensed as 4 x 2 x 16 = 128 cores, not 96. Those 128 cores include 128 x 0.25 = 32 TiB of raw vSAN capacity. If the cluster needs 50 TiB raw, you license 18 TiB of vSAN add-on capacity. Remember that the entitlement is raw capacity, before RAID-5/6 or mirroring overhead.

VVF add-ons

  • vSAN add-on (additional TiB)
  • VMware Live Recovery Cloud
  • Site Recovery Manager
  • VMware Avi Load Balancer

Licensing changes in VVF 9.1

VVF 9.1 became generally available on May 5, 2026. The FAQ lists these licensing changes:

  • 25-character license keys are replaced by subscription license files, created in the Business Services console.
  • VCF Operations is required: license files are uploaded to VCF Operations and assigned to vCenter instances.
  • A new headless VCF License Server appliance is deployed and lifecycled automatically during installation or upgrade.
  • Perpetual licenses cannot be upgraded to 9.1; you must move to subscription first.
  • There are no standalone vSphere Standard or Enterprise Plus SKUs for 9.x; 9.x is only available as VVF or VCF.

Deployment and platform notes

  • Greenfield VVF 9.x is deployed with the VCF Installer, which also deploys VCF Operations. For a small lab walkthrough see deploying a minimal VCF 9.0 lab.
  • vSphere Virtual Volumes (vVols) are deprecated starting with VVF/VCF 9.0 and will be removed in a future release.
  • vSAN still requires certified hardware from the Broadcom Compatibility Guide (vSAN ReadyNodes).

Is VVF enough, or do you need VCF?

VVF fits a classic vSphere estate that wants DRS/HA, a modest amount of vSAN, Kubernetes and proper monitoring. Choose VCF when you need NSX overlay networking and security, VCF Automation (self-service/private cloud), fleet lifecycle management or 1 TiB/core of vSAN. The detailed feature matrix is in the product line comparison.

Further reading

Automating counting cores & TiBs for new VMware…

Automating counting cores & TiBs for new VMware vSphere Foundation (VVF) and VMware Cloud Foundation (VCF) SKUs

Automating counting cores & TiBs for new VMware…

Happy New Year! 🥳🎉🥂 At the end of 2023, we announced two new offerings called VMware vSphere Foundation (VVF) and VMware Cloud Foundation (VCF) that drastically simplifies our overall vSphere-based portfolio and licensing model. To help our users understand the new licensing model which uses both CPU cores and TiB (for vSAN storage sizing), I […]


VMware Social Media Advocacy

Getting started with VCF 4.0 Part 3 – vSphere…

Getting started with VCF 4.0 Part 3 – vSphere with Kubernetes in a Workload Domain

Getting started with VCF 4.0 Part 3 – vSphere…

At this point, we have a fully configured workload domain which includes an NSX-T Edge deployment. Check here for the previous VCF 4.0 deployment steps. We are now ready to go ahead and deploy vSphere with Kubernetes, formerly known as Project Pacific. Via SDDC Manager in VMware Cloud Foundation 4.0, we ensure that an NSX-T Edge is available, and we also ensure that the the Workload Domain is sufficiently licensed to enable vSphere with Kubernetes. Disclaimer: “To be clear, this post is based…Read More


VMware Social Media Advocacy

Getting started with VCF 4.0 Part 2 –…

Getting started with VCF 4.0 Part 2 – Commission hosts, Create Workload Domain, Deploy NSX-T Edge

Getting started with VCF 4.0 Part 2 –…

Now that a VCF 4.0 Management Domain has been deployed, we can move onto creating our very first VCF 4.0 Virtual Infrastructure Workload Domain (VI WLD). We will require a VI WLD with an NSX-T Edge cluster before we can deploy Kubernetes on vSphere (formerly known as Project Pacific). Not too much has changed in the WLD creation workflow since version 3.9. We still have to commission ESXi hosts before we can create the WLD. But something different to previous versions of VCF is that today in…Read More


VMware Social Media Advocacy

Getting started with VMware Cloud Foundation…

Getting started with VMware Cloud Foundation (VCF) 4.0

Getting started with VMware Cloud Foundation…

On March 10th, VMware announced a range of new updated products and features. One of these was VMware Cloud Foundation (VCF) version 4.0. In the following series of blogs, I am going to show you the steps to deploy VCF 4.0. We will begin with the deployment of a Management Domain. Once this is complete, we will commission some additional hosts and build our first workload domain (WLD). After that, we will deploy an NSX-T 3.0 Edge Cluster to our Workload Domain. The great news here is that…Read More


VMware Social Media Advocacy