I have an array that supports VAAI file based cloning. The vCloud settings do not seem to match up with the expected behavior.
Here is what I am experiencing:
Setup 1:
VAAI for fast-provisioning enabled on datastore (only using a single datastore in the storage profile).
Fast-provisioning disabled on the OVDC.
Test 1:
Clone a vApp from the catalog that has a chain length of 1.
Result 1:
VAAI is used to clone VM <-- This shouldn't be happening according to my settings on the OVDC
I have the ability to resize the disk and the chain length is 1 for the VM and that item in the catalog.
Setup 2:
VAAI for fast-provisioning enabled on datastore
Fast-provisioning enabled on the OVDC
Test 2:
Clone a vApp from the catalog that has a chain length of 1.
Result 2:
The VM's inside the vApp now has chain length of 2 and so does the VM in the catalog, showing that VAAI was not used and old COW method was used"
I also now cannot resize the hard disk of the VM. Error: "The hard drives of the virtual machine "Server1" may not be modified, once created. This is a result of COW based fast-provisioning.
This also causes Test 1 to now result differently because when cloning a fast-provisioned VAAI is not used. This requires that the catalog item be reset back to chain length of 1 by consolidation, which I ran into another issue with. The only way to really consolidate seems to be do a consolidation in the catalog, then find the VM in vCenter and perform the consolidation. Then Test 1 will function again.
This is causing me to not be able to enable fast-provisioning for some OVDC's while not for others when using VAAI based fast-provisioning.
Anyone else notice this?
Running vCloud 5.1.2