Don't think that's really accurate.
You don't have to use C with Python, and there's no VM to worry about. CPython* just happens to be the most popular implementation.
Clojure (by and large)* requires the whole Java infrastructure, and that is a nonstarter for many.
There are Clojure implementations that run on JS runtimes, the .Net CLR, the Erlang BEAM runtime, etc.
CPython comes with its own VM: are you saying the issue is "you need to install 2 things instead of 1"?
I think, though, that the things that Clojure gets right go way beyond just the JVM, though. Clojure's approach to nil punning, for example, is really well thought out.
I don't have anything against Clojure (well, I'm a little negative on the JVM), but I personally don't see any reason to move to it from Common Lisp.
On the other hand, I'd miss CLOS, and I feel like CL has a better/more consistent design. Something about Clojure always feels like they're "winging it".
In a nutshell, nil punning is a thing in lisps (and some other languages) where the null value can have different meanings in different contexts. It's comparable to Python's concept of "truthiness" and "falsiness", but more so.