First off I would have posted your question in the SQL 2012 forum as Always on Availability Groups are only supported by SQL 2012.
Anyway. I am in the process of creating a proof of concept for a similar setup.
We currently use multiple 2 node clusters to support our DB infrastructure, we logship from several of the SQL clusters to a reporting server and have transactional replication sharing data between clusters all sharing the same distributor.
From an initail discussion with MS, they have confirmed that they will support a virtual windows cluster, but they were unclear if they would support a SQL Clustered Install ontop of this platform.
Our current setup in the POC is 5 Virtual Windows 2012 servers forming a windows cluster. Each of the 5 servers has a standalone SQL 2012 Install. We have two AG's defined each AG has 3 participating servers (1 primary, 1 Readable Synchronous Secondary, 1 Non Readable non synchronous secondary.
Only one of the servers participates in both AG's.
The problem we are working on at the moment is replication, from what I can tell AG's do not support distribution, so we have created 2 other VM's running Windows 2012 and SQL 2012 and they run as a SQL cluster and the distributor is installed here. All publications for databases within the AG's use this as a remote distributor. The subscribers are also part of the availablity groups. But they also cross groups.
This is something to consider if you are looking at this with a view to using AG's to provided for HA \ DR.
MCITP SQL 2005, MCSA SQL 2012