Creating a Virtual Machine
When creating a virtual machine (VM), the administrator selects a storage policy and the wizard displays a list of compatible datastores to select as storage. This ensures that storage can be selected based on storage policy and the virtual volume (vVol) is created from a storage container with matching capabilities. As a result, DataCore SANsymphony creates a vVol virtual disk (vDisk) from pools with compatible capabilities and then binds these vDisks to the VM.
When a VM is created:
- Typically there are three associated vDisks created in DataCore SANsymphony: one for the configuration data, one for the virtual disk hard disk (vmdk file), and one for the swap data (vswp file). The names of these vDisks are based on the VM name. For any additional hard drive, an additional vDisk is created.
Do not delete any vDisks associated with a vVol in VMware.
- The vmdk and configuration file for the vVol appears in the configuration during the VM creation.
- The swap file appears in the configuration when the VM is powered on, and disappears from the configuration when the VM is powered off.
- When the VM is powered on, the vVol is bound to the protocol endpoint (PE), and the vmdk file is made available to the hosts. The vmdk file is displayed in the Hosts panel under the ESXi hosts and under the associated PE. Since vDisks are not served to the hosts, there will be no serve information or front-end (FE) paths displayed in the DataCore Management Console. Only mirror paths are displayed. Hosts only see PE, which directs and connects the VM to the corresponding vVol. I/O goes directly to the vVol.
- Supported features enabled on the vDisk template are enabled on the vDisks when the VM is created.
Configuration Size Increased in vCenter 8.0 U1
The size of config-vvol objects has been increased from 4 GB to 255 GB. For more information, refer to the following article: https://kb.vmware.com/s/article/90791.
Also see: