A VVol datastore, is not a file system, so it is not a traditional datastore. It is just a capacity quota. So when you “mount” a VVol datastore, you aren’t really performing a traditional mounting operation as there is no underlying physical storage to address during the mount. So instead of mounting some storage device, you are mounting what is called a storage container. This is the meta data object that represents the certain amount of capacity that can be provisioned from a given array. An array can have more than one storage containers, for reasons of multi-tenancy or whatever.

In a VMFS world, when you go to create a new datastore, you pass it the serial number of the storage you want to format with VMFS. You know that serial, because, well, you created the storage device. When you “mount” a VVol datastore, instead of a device serial, you supply the storage container UUID. It comes in the form of vvol:e0ad83893ead3681-b1b7f56a45ff64f1. Of course the characters will vary a bit.

On the FlashArray, we currently have a single default storage container. We generate the UUID based off of the array serial number–this is so we can always regenerate it in the same way (it will be unique, but not random). In short we take a double hash, replace two bits in order to specify it is a type-3 UUID, and then return it in the form VMware requests.

When we add support for multiple VVol datastores, the process to get those UUIDs from the array will be different, and more streamlined.

Normally, you don’t need to understand this. In vCenter, you just go to new datastore, you see the storage container, and go on your merry way selecting it and mounting it.

If you want to script it though, it could be helpful to know what this ID is (duh). There is an API in the SMS API to queryContainer() that when left with no parameters, will return all available storage containers. If the storage container has not been mounted yet, that is the only way to find out the UUID. Unfortunately, the ability to call this API is almost nowhere in the commonly used tools (AFAIK). vRO might be the exception.

So, in PowerShell, I have made it easy, by writing a PowerShell cmdlet for you. But here is the code if you want it. And also in two other languages. We are running the assumption you have the array ID and it comes in the form of 184b1c58-c285-4eba-8ac7-2e7ac3618bf9


Here is an example script that generates the correct UUID. PowerShell was a little goofy because the GUID generator seems to flips some of the bits so I had to flip them back.

Find it here on GitHub:



I don’t know how many will use this, but I have been getting into a Go a bit, so I figured I’d use this as an exercise to learn. Note you need to install the UUID package to get this to work.

This is posted on my Github here:


Python 2.7

And now in Python 2.7. Very similar to Go

Find it here on GitHub:



Okay one more because why not?

Find it here on GitHub: