Highly available virtualized SQL Server on 2 ESXi hosts and one SAN storage

Be careful in selecting and naming your HA solution.

• Always On Availability Groups (AG) maintains secondary copies. Usually, roughly double the space and IOPS on the same array is undesirable.
• Always On Failover Cluster Instances (FCI) are the suggested way to use one shared disk array for MS SQL. Only one copy, in theory simpler but if the one array fails the database is down.

Because SQL uses Windows Server Failover Clustering (WSFC), and FCI is the one copy of the data solution, shared storage requirements and guidelines apply. Use RDMs, or in guest iSCSI initiators, for clusters across physical hosts. Basically, the cluster needs direct access to shared LUNs.

Edit: you asked about VVols. As of ESXi 6.7, yes you can use VVols for FCI shared storage, due to more complete SCSI support. Read up on the feature and its requirements: Virtual Volumes now supports WSFC.

Capacity planning is necessary, both if the array physical disk layout can be changed with pools/groups or not. Determine whether the limiting factor is IOPS or capacity.

From what I have tested, consider using AlwasysOn Availability Groups (AGs). Unlike SQL Server Failover Cluster Instance (FCI), AlwasysOn Availability Groups (AGs) performs slightly faster.

Source: my topic/question about testing SQL Server performance. What may increase the latency 3-4 times for SQL FCI the database?