Yaniv,
Just for clarification of some concepts that are inherent to VCS:
In terms of how Service Groups (Association of Resources) are located within a cluster, it can be active on any one or more nodes at any given time. That being said, Service Groups operate at whatever layer VCS is installed in. I.e. If VCS is installed on the base Windows OS, it will operate at the Physical layer of each host it is configured for in the cluster. Conversely, if VCS is installed in a Virtual Machine, on ESX for example, it will exist entirely within the boundaries of that VM or any subsequent nodes it is assigned to. Additionally however, a service group can failover between Physical and Virtual platforms (assuming all pre-reqs are met). Either way, VCS does not differentiate between the two.
In terms of the output you provided, Service Group GSA_SG is currently active on System DBSB and offline on DBSA. Therefore VCS has to be installed on the base Windows layer on both Nodes. Please provide the following output:
C:\>hagrp -state GSA_SG
I am not quite clear on what you mean by "certain application visible on certain virtual machine." There appears to be a discrepancy with what you refer to as the Physical Host and what VCS is identifying as a cluster node. The -sys flag is meant to specify a specific cluster node.
In terms of Virtual Names/Computers and how they exist within AD and Windows, those actions are performed by the LanMan resource and as such when brought online it associates an IP address with a Virtual Name in whatever OU you would assign.
VCS will only report back the status of an AD Computer Objects that assigned by the LANMAN resource. That being said, you mentioned V1 and V2 which I am presuming are Virtual Names/instances for your application. If you have properly configured your LANMAN resource, then whichever node the service group is active will correspond the where the IP address and virtual name are assigned.
I apologize for the long-winded explanation :o)
Joe D