As @paul driver notes, your class-maps appear to be "mixed up". What's confusing, your class maps are setting DSCP values (BTW, scavenger, by RFC, is CS1; it's not default, i.e. BE) and not matching anything. Further, your policy map doesn't show any class maps with their class names.
Paul also notes you don't need "qos pre-classify" on the tunnel interface (if being used). That's correct. It's only needed if you need to match pre-encapsulated packet fields (for matching) beyond the ToS byte (which is copied from original packet) if service policy applied on physical interface.
BTW, Paul's suggested policy map doesn't show a bandwidth allocation for class-default. Don't recall Cisco guaranteeing what bandwidth class-default would obtain w/o it (we might assume remaining available, but that's an assumption). So, I recommend it's good practice to explicitly set it. If you do want class-default to use whatever is left over, you might have:
class class-default
bandwidth remaining percent 100
fair-queue
Cannot be sure, as I'm unfamiliar with C11xxs, but CBWFQ, before HQF, QoS only supported FQ in class-default. Otherwise, in both pre-HQF and post-HQF, I've used service policies on other Cisco routers' tunnels, using FQ.
