You must complete a series of steps to configure your Virtual Volumes environment.

Follow guidelines in Before You Enable Virtual Volumes.


Your Virtual Volumes environment must include storage providers, also called VASA providers. Typically, third-party vendors develop storage providers through the VMware APIs for Storage Awareness (VASA). Storage providers facilitate communication between vSphere and the storage side. You must register the storage provider in vCenter Server to be able to work with Virtual Volumes.


You use the New Datastore wizard to create a virtual datastore.


ESXi hosts use a logical I/O proxy, called protocol endpoint, to communicate with virtual volumes and virtual disk files that virtual volumes encapsulate. Protocol endpoints are exported, along with associated storage containers, by the storage system through a storage provider. Protocol endpoints become visible in the vSphere Web Client after you map a storage container to a virtual datastore. You can review properties of protocol endpoints and modify specific settings.


If your ESXi host uses SCSI-based transport to communicate with protocol endpoints representing a storage array, you can modify default multipathing policies assigned to protocol endpoints. Use the Edit Multipathing Policies dialog box to change a path selection policy.

You can now provision virtual machines on the virtual datastore. For information on creating virtual machines, see the vSphere Virtual Machine Administration documentation.

For troubleshooting information, see the vSphere Troubleshooting documentation.