To get access to the RHEV-M 3.0 beta, you must have an active Red Hat Enterprise Virtualization subscription. Go to this RHN page to see links to the beta channels. See this page for discussion around the beta. This is the official announcement.
As planned (see part 2) I installed RHEV-M 3.0 beta management server inside a guest on the first host:
There are various reasons for using a guest: (1) The management server has some pretty heavyweight dependencies, like Java, JBoss and FreeIPA, so keeping it in a guest is good for isolation. (2) It means I can easily turn the management server off when I’m not using RHEV-M, and fire up other guests for other work.
On the other hand, RHEV-M has some serious requirements. It needs 2GB of RAM (I found that in fact you have to give it strictly > 2GB of RAM before it will even install), and recommends using 4GB of RAM. The requirements are no joke either, since once it’s running you’ll see a huge JVM process consuming a constant 2GB of RAM and 10% of CPU even when nothing is happening. Welcome to the world of Java …
I also gave the guest 100GB of disk space, thinking it would need a large amount, but in fact it has only used 5GB.
Installation was very straightforward. First I created an ordinary RHEL 6.1 guest (using virt-install). Then I registered the guest with RHN, added the RHN channels, and followed the instructions, and it went mostly without a hitch.
This version runs on Linux, but you still need Internet Explorer to access the Admin Portal. (Note: This requirement will be removed in the next version: RHEV-M 3.1).
Thus I had to use a Windows 7 guest locally in order to get these screenshots:
There’s nothing much I can do in the UI at the moment, because I have no hosts to manage yet. Next week I should have some hard drives.