vvols had a lot of issues initially, both on 3PAR and VMware side.
for us the lack of peer persistance support is an issue, we have quite a few metro clusters.
We are a VMware premier partner and got early notice on vvolsv2/VASA3 and decided to wait.
Still waiting.... 6.5U1 released, but 3.3.1 still in controlled release.
Think we'll wait until general availability for testing and wait for 3.3.1U1 before we even consider any production.
Been challenging HPE and VMware for references to customers on our scale and there are none...
Not sure if I want to be the first to break vvols on an array...