If you need them both to work at the same time towards the same peer address in the other end, you can use a fvrf to assign a default route that points out that dsl interface, and then use that vrf in your ipsec profile.
so something like this :
ip vrf dsl
!
interface dsl-something-or-other
ip forwarding vrf dsl
!
ip route vrf dsl 0.0.0.0 0.0.0.0 x.x.x.x
!
crypto keyring test vrf dsl
pre-shared-key address x.x.x.x x.x.x.x key xxxx
!
crypto isakmp profile test
keyring test
match identity address x.x.x.x 255.255.255.255 dsl
!
crypto ipsec transform-set test esp-aes 256 esp-sha-hmac
!
crypto ipsec profile test
set transform-set test
set isakmp-profile test
!
interface tunnelx
tunnel vrf dsl
tunnel protection ipsec profile test
This should make a new tunnel interface, so you will probably need either a new dmvpn on the hub as well, or you could try the same dmvpn config, just with another GRE address, not sure if that will work. But the config will allow you to have both your regular dmvpn and one using the dsl, by seperating the routing table into a global that handles your regular dmvpn and the dsl one that handles the dmvpn over dsl.
