Metab,
If i am reading this right, within each vlan you would like users from vlan 1 and vlan 10 to communicate with anyone in remaining vlans (for example 5,7,15... whatever number).
So in your above configuration.. this is what you are allowing within each vlan (in this example vlan 49):
10.64.10.x can do and see anyone
10.64.1.x can do and see anyone
everyone destined to everything else is dropped. Your deny ip any any at the end does nothing.. VACL's are like route-maps and a deny just means that there isn't a match on that particular Access-map statement. When that happens there is no VACL permit 20 with action forward so it denies the traffic. It basically could be removed.
So with that logic, any traffic within that vlan (including internet) will be dropped.
Here is what i would do if you want to use VACL's. If you have Vlan SVI's that might be a better option with L3 access-lists if your looking for alternatives.
List out your current VLAN ip subnets and summarize if possible
Vlan 1 = Subnet 1
Vlan 2 = Subnet 2
ip access-list extended DROP
permit ip any
permit ip any
** exclude vlan/subnet 10 and 1
vlan access-map VACL permit 10
match ip address DROP
action drop
vlan access-map VACL permit 20
action forward
vlan filter VACL vlan-list 49
Do this for all vlans except for 10 and 1.
For 10 and 1
ip access-list ext VLAN10
permit ip 10.64.10.0 0.0.0.255 any
permit ip any 10.64.10.0 0.0.0.255
ip access=list ext VLAN1
permit ip 10.64.1.0 0.0.0.255 any
permit ip any 10.64.1.0 0.0.0.255 any
vlan access-map VACL10 permit 10
match ip address VLAN1
action drop
vlan access-map VACL10 permit 20
action forward
vlan access-map VACL1 permit 10
match ip address VLAN10
action drop
vlan access-map VACL1 permit 20
action forward
vlan filter-list VACL10 vlan-list 10
vlan filter-list VACL1 vlan-list 1
Really might look at some Layer 3 acls as suggested before though
Regards,
Nate
