It's more comparable to virtualenv with virtualenvwrapper. Also, it manages multiple versions of Ruby (AFAIK virtualenv was coupled to a single version of Python) and has a per-directory dotfile (that way, when I switch to ~/Projects/something rvm automatically switches to correct ruby and gemset).
It generally feels more 'complete' to me.
I didn't do any serious work with virtualenv in quite some time, so this may have changed.