Skip to main content
NetApp Knowledge Base

VASA Provider: New VM creation fails when storage capability profile used does not match backing storage

Last Updated:

Applies to

  • ONTAP Tools for VMware vSphere 9.10
  • ONTAP Tools for VMware vSphere 9.11


To illustrate this issue:

  1. We have a vVol datastore called NFS_VVOL_01 with an assigned backing flexvol that has a Storage Capability Profile (SCP) of "Bronze":

VASA Provider

2. We then attempt to create a new virtual machine (VM) using a VM Storage Policy based off of a different SCP:

VM Storage Policy

3. The VM creation fails:

VM creation fails

4. The storage capabilies of the SCP assigned to the datastore's backing flexvol and the one used during new VM creation are identical:

SCP assigned


Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.