I know this is an old post, but anyway... the cat9000v's need a lot of resources. If your CML VM doesn't have enough CPUs or memory, the cat9000v's won't start. I had to get a bigger server last year for this reason.

So now you know why the SLA fails. You could try pinging the first router in the ISP's network, the one upstream from your domestic router. 

One other thought is that maybe the ISP blocks 8.8.8.8 because they want to force use of their DNS. Can you ping 8.8.8.8 from the computer that gets the 34 address? You might need to change your sla/track to a different ip.

Ok so the way to troubleshoot this is to remove all the features, test, then put the features back one by one. Remove the nat and the service policy. Check the interface negotiated matching speed & duplex. If it's good, start putting feature back on.

You have no default route on gi0/0/0 because the track is wrong on the route. Fix that and send the route table and show ip sla sum. and show track.