Reading Time: 2 minutes

The new VMware Cloud Foundation 9.0 comes with a long list of deprecated features!

One of this the VMware vSphere Virtual Volumes (vVols) introduces for the first time in vSphere 6.0. They are an integration and management framework to enable external storage to become VM-aware storage.

But vVols got some limitations (like replication in the first release, or backup via SAN mode) and a huge problem: not all Virtual Volumes implementation are the same (some storage vendors do it very well, but not all).

They remain a good idea, but with too many limitation, including a big dependency by vCenter Server… without it you cannot allocate space on a vVol datastore (that means that vCenter VM should stay on a NON vVol datastore).

After 10 years, VMware vVols capabilities will be deprecated beginning with the release of VMware Cloud Foundation (VCF) version 9.0 and VMware vSphere Foundation (VVF) version 9.0 and will be fully removed in VCF/VVF 9.1. As a result, all vVol certifications for VCF/VVF 9.0 will be discontinued effective immediately.

Support for vVols (critical bug fixes only) will continue for versions vSphere 8.x, VCF/VVF 5.x, and other older supported versions until end-of-support of those releases.

Limited-time support may be considered on a case-by-case basis for customers desiring vVols support in VCF/VVF 9.0. Such customers should contact their Broadcom representative or Broadcom support for further guidance.

So, it’s time to move to a VMFS or NFS or vSAN datastore!

Share