RHEV-M (piece one of a two part product) was originally created by Qumranet, along with the proprietary mgmt protocol it uses for kvm. It's written as a .Net application (requiring W2K3r2 and SQL Server/Express, etc.). The RHEV-H side is designed to be a non-seen Linux distro running kvm. The idea is to shield all of the RHEV-H under the controls of RHEV-M.

Red Hat originally looked at existing ways to run the .Net app... but that would involve things .Net on Linux (e.g. Mono) and Red Hat feels that's too risky. So the plan (AFAIK) is to rewrite RHEV-M as a JBoss Java app (sorry, still two pieces, you'll need a JBoss platform).

AFAIK, there's no way currently to get at any piece of RHEV-M or RHEV-H (for that matter). RHEV-H is an appliance style implementation... if you've ever seen this, that means the resulting platforms is done by unrolling files... the result is considered to be volatile. It's not well documented. It makes rolling in a kernel parameter (for example and from own experience) rather difficult since you have to unroll things, change things and roll things back up.

RHEV-H is a fairly typical appliance style Linux deployment, if you've ever used one. Just might be a bit cumbersome for users that have never done anything like that.

And, remember that it requires a SEPARATE subscription. It's NOT RHEL. It's considered a totally different thing.

If I were a CentOS user today, I'd just use plain ole standard kvm. If you HAVE to mimic Red Hat exactly, you'll need to wait until Red Hat makes those pieces available (if they haven't already) and wait for CentOS to figure out the best way to deploy it.