resource-agents: Fix migration mapping behavior w/ virsh
    
    Consider a two node cluster. The hostname of the nodes
    are 'sk010001' and 'sk010002'.  Each nodes has two bonded
    network interfaces for public and private communications.
    The hostname matches the hostname of the IP address on
    public network.
    
    Node1: sk010001
     bond0 (for public network) : 172.22.51.1    sk010001
     bond2 (for private network): 172.22.48.131  sk010001-hb
    
    Node2: sk010002
     bond0 (for public network) : 172.22.51.2    sk010002
     bond2 (for private network): 172.22.48.132  sk010002-hb
    
    In cluster.conf, a migration mapping is used to specify
    that the private interfaces should be used for migration traffic.
    Unfortunately, when doing a live migration, while the traffic
    should use the -hb interfaces, bond0 is used.
    
    This is because the vm.sh agent uses the following command
    for live migration from sk010001 to sk010002:
    
      virsh migrate --live su21k003 \
    	qemu+ssh://sk010002-hb/system
    
    This is not enough to ensure the guest goes over the private
    interface.  The --migrateuri option of 'virsh migrate' is needed
    for it.  The following command should be executed instead:
    
      virsh migrate --live su21k003 \
    	qemu+ssh://sk010002-hb/system tcp:sk010002-hb
    
    Resolves: rhbz#596918
    
    Signed-off-by: Lon Hohberger <lhh@redhat.com>