GE1/0/1
ip binding vpn-instance vrf1
ip address 192.168.1.1 255.255.255.0
GE 1/0/2
ip binding vpn-instance vrf2
ip address 192.168.2.1 255.255.255.0

In order to reproduce this
scenario I used this topology(with a similar switch) to simulate :
The configuration from SW1 :
#
vlan batch 2
#
ip vpn-instance test
ipv4-family
route-distinguisher 100:1
import route-policy 1
vpn-target 1:1 export-extcommunity
vpn-target 1:1 import-extcommunity
#
ip vpn-instance test2
ipv4-family
route-distinguisher 100:2
export route-policy 2
vpn-target 1:1 export-extcommunity
vpn-target 1:1 import-extcommunity
#
interface Vlanif1
ip binding vpn-instance test
ip address 1.1.1.1 255.255.255.0
#
interface Vlanif2
ip binding vpn-instance test2
ip address 2.1.1.1 255.255.255.0
#
interface GigabitEthernet0/0/1
port link-type access
port default vlan 1
#
interface GigabitEthernet0/0/2
port link-type access
port default vlan 2
#
bgp 1
router-id 1.1.1.1
#
ipv4-family unicast
undo synchronization
#
ipv4-family vpn-instance test
import-route direct
#
ipv4-family vpn-instance test2
import-route direct
#
PC1 :
PC2:
Result :

So, using the same vpn-target for both VRFs was enough to make the ping working between these 2 hosts. Hope this is useful :)