If the system behaves as it should, the numbers in the VMCommitted and VMAllocated will never reside in virtual memory, unless the Working Set limit High has been passed, and by then Windows are only allowed to swap the amounts above that limit. QVS, per default, makes sure that it's working set is in physical memory, since if you would have any (considerable) amounts of ws data in virtual memory, response times on data access would be horrible.
Swapping occurs on a QVS system, but during regular operations, not by QVS itself. Windows are mainly responsible for swap operations system wide, and that is as designed.
Therefore, there are no real meaning in parting QVS working set memory in physical and virtual memory counters, since it basically are no data in virtual memory, unless there are a memory exhaustion problem on the system.