6.7

Table Of Contents
Table 221. esxcli storage vvol commands (Continued)
Namespace Command Option Description
esxcli storage vvol
storagecontainer
list
abandonedvvol scan
List all available storage containers.
Scan the specified storage
container for abandoned VVols.
esxcli storage vvol vasacontext get
Show the VASA context (VC UUID)
associated with the host.
esxcli storage vvol vasaprovider list
List all storage (VASA) providers
associated with the host.
Virtual Datastore Is Inaccessible
After you create a virtual datastore, it remains inaccessible.
Problem
The vSphere Client shows the datastore as inaccessible. You cannot use the datastore for virtual
machine provisioning.
Cause
This problem might occur when you fail to configure protocol endpoints for the SCSI-based storage
container that is mapped to the virtual datastore. Like traditional LUNs, SCSI protocol endpoints need to
be configured so that an ESXi host can detect them.
Solution
Before creating virtual datastores for SCSI-based containers, make sure to configure protocol endpoints
on the storage side.
Failures When Migrating VMs or Deploying VM OVFs to Virtual
Volumes Datastores
Your attempts to migrate a virtual machine or to deploy a VM OVF to virtual datastores fail.
Problem
An OVF template or a VM being migrated from a nonvirtual datastore might include additional large files,
such as ISO disk images, DVD images, and image files. If these additional files cause the configuration
virtual volume to exceed its 4-GB limit, migration or deployment to a virtual datastore fails.
Cause
The configuration virtual volume, or config-VVol, contains various VM-related files. On traditional
nonvirtual datastores, these files are stored in the VM home directory. Similar to the VM home directory,
the config-VVol typically includes the VM configuration file, virtual disk and snapshot descriptor files, log
files, lock files, and so on.
vSphere Storage
VMware, Inc. 299