Category Archives: RHEV

Red Hat Enterprise Virtualitzation

Nested RHEV-H 3.x and VMware ESXi 5.5

I was trying to setup a RHEV laboratory in my ESXi but I wasn’t unable to approve my host.

In RHEVM appeared an error in the GUI like this one (check your Events tab):

Command returned failure code 1 during SSH session '[email protected]'

But in RHEVM logs there was another latent issue, checking /var/log/ovirt-engine/engine.log :

2014-04-27 12:17:20,814 ERROR [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation x.x.x.x: Failed to execute stage 'Setup validation': Hardware does not support virtualization
2014-04-27 12:18:48,555 ERROR [org.ovirt.engine.core.bll.InstallVdsCommand] (pool-4-thread-49) [1c11a8d3] Host installation failed for host 4eba0c68-4370-4223-8271-831cccf3a64e, x.x.x.x.: Command returned failure code 1 during SSH session '[email protected]'

So in order to enables nested virtualization of RHEV-H in VMware ESXi 5.5u1 we have to add 2 new values in our vmx file:

featMask.vm.hv.capable = "Min:1"
vhv.enable = "TRUE"

After adding them I was able to approve the host without any further issues.

Upgrading RHEV-M 3.3 to RHEV-M 3.4 Beta

In order to update RHEV Manager from 3.3 to 3.4 beta we can follow this procedure:

yum-config-manager --enable rhel-6-server-rhevm-3-beta-rpms
yum-config-manager --enable rhel-6-server-beta-rpms
yum-config-manager --enable rhel-6-server-rhevh-beta-rpms
yum update rhevm-setup -y
yum update rhevm-dwh rhevm-reports -y
yum update rhev-hypervisor6 -y

If upgrading rhevm-reports fails is due to this bugzilla:

As a workaround first we need to upgrade jasper reports server and install openjdk dev rpm and re-run engine-setup once more:

yum update jasperreports-server-pro -y
yum install java-1.7.0-openjdk-devel.x86_64 -y

How to upgrade our RHEV-H hypervisors with RHEVM?

Once we’ve installed RHEVM and our RHEV-H’s how should I upgrade the hypervisors?

In order to do so, on the RHEVM machine, we need to install the isos images of RHEV-H:

yum install rhev-hypervisor6.noarch

NOTICE: If you’re unable to install this package add the following channel:

rhn-channel --add -c rhel-x86_64-server-6-rhevh

And we’ll notice that /usr/share/rhev-hypervisor/ contains the iso images of RHEV-H:

ls /usr/share/rhev-hypervisor/

Once it’s installed, we can put our RHEV-H into maintenance mode, and will see this option:

  • Host is in maintenance mode, you can Activate it by pressing the Activate button. If you wish to upgrade or reinstall it click here.
And just click “here” and select which RHEV-H iso image are you going to use:
  • rhevh-latest-6.iso

And that would be it, let RHEVM install the upgrade and the node would be automatically rebooted with the newer version of RHEV-H.


How to install RHEV Manager (RHEVM) Report?

Did you know that with RHEVM we can generate and create awesome reports?

If not, please, give it a try and install and configure RHEVM reports:

yum install -y rhevm-reports.noarch

Once it’s configured you’ll need to access to this URL:

  • https://<FQDN>:8443/rhevm-reports/

Remember that the default administrator user it’s called: rhevm-admin

How to install RHEV Manager (RHEV) Web Admin? (Technology Preview!)

In RHEV 3.0 we’re very near to ditch out our windows clients for administrating RHEVM plataform once and forever.

In order to do so we need to install the new HTML5 webadmin portal (normally it’s installed by default):

yum install -y rhevm-webadmin-portal.x86_64
service jbossas restart

And then you’ll need to access to this URL:

  • https://<FQDN>:8443/webadmin/webadmin/WebAdmin.html

Finally, take into account that:

  • Under Chrome works quite well but remember that there’s no SPICE plugin for Chrome web browser. So if you need to see the console of your guest, Firefox is the way to go.
  • Be aware that is not yet 100% functional as the other Administration Portal because it’s just in technology preview!

How to install RHEV Manager 3.0 (RHEVM)?

In order to install RHEVM we’ll need 2 things:

  • RHEL 6.2 x64
  • RHN account

Afterwards we’ll need to install RHEL 6.2 x64 with @base channel and update it to the minor release available once it is fully installed:

yum upgrade -y

And then we’ll proceed installing the necessary channels for RHEVM:

rhn-channel --add -c rhel-x86_64-server-6-rhevm-3
rhn-channel --add -c jbappplatform-5-x86_64-server-6-rpm
rhn-channel --add -c rhel-x86_64-server-supplementary-6
rhn-channel --add -c rhel-x86_64-server-6-rhevh

And as a last step we’ll only need to install RHEVM and configure it:

yum install -y rhevm

Afterwards you’re good to go to the RHEVM Administration Portal:

  • http://<FQDN>:8080/
  • https://<FQDN:8443/RHEVManager

REMEMBER that RHEV Manager only works with clients that can satisfy this requirements:

  • Microsoft Windows (7, XP, 2003 or 2008) with Internet Explorer 7 and above
  • Microsoft .NET Framework 4
If you want to use a Linux client check my future posts 😉

Single Sign On in RHEV3 using GDM and Active Directory

As per my previous post we should have Active Directory up and running in our RHEV-M.

So how about setting up SSO on our RHEL guests? In order to do that we should follow this simple procedure.

First of all we need to install our rhev agent that is found in a special channel and winbind client:

rhn-channel --add --channel=rhel-x86_64-rhev-agent-6-server
yum install rhev-agent rhev-agent-gdm-plugin-rhevcred samba-winbind-clients

Next of all we need to activate AD authentification on our guest, for example (RHEVM is our test Domain):

  User Account => Winbind
  Winbind Domain => RHEVM
  Security Model => ads
  Winbind ADS Realm => RHEVM
  Winbind Domain Controller => ad.rhevm.test
  Template Shell => /bin/bash
  Join Domain  => Joined domain RHEVM.

If is not working double check your configuration files and DNS resolution:


And finally, just in case, check that winbind is properly working, we could check some users/groups for example:

wbinfo -t
wbinfo -u
wbinfo -g
getent passwd "RHEVM\testuser"

As a last step, check that we can login/sudo with an AD user on this guest:

su - 'RHEVM\testuser'
ssh 'RHEVM\testuser'@localhost

Finally restart GDM daemon and rhev-agent service:

service rhev-agentd restart
pkill -f gdm-binary

And try to Single Sign On through GDM! It should work!

If it doesn’t work put in debug mode rhev-agent and try to figure out why is not working:

vi /etc/rhev-agent.conf
service rhev-agentd restart
tail -f /var/log/rhev-agent/rhev-agent.log

How to connect RHEV 3.0 IPA to Active Directory?

In a default installation we have two methods of authentication:

But, how about connecting our IPA to an Active Directory? Piece of cake! We just need to add it through the command line:
rhevm-manage-domains -action=list
rhevm-manage-domains -action=add -domain='your.nice.domain' -user='' -interactive
service jbossas restart
After that we can check that our Active Directory is correctly up and running, trying to connect it through:
rhevm-manage-domains -action=list
rhevm-manage-domains -action=validate
If it validates, all should be fine! Just try to log in with your admin IPA user and set up some users/perms from your AD, and then just authenticate with your user/pass of the AD.
If it doesn’t work just take into account:
  1. Remember to restart jbossas service after setting up your AD domain!
  2. On the UserPortal/RHEVManager remember to select the correct domain from the combobox!
  3. If you can add your AD domain, did you try to add it with another administration user of your AD?
And just in case you just broke IPA and don’t remember your internal admin password ([email protected]), you can change it through:
rhevm-config -s AdminPassword=<newpassword>
service jbossas restart


Well, I need to improve my broken engrish, so…

Did you know that Red Hat open sourced RHEV? And the result was oVirt!

So that’s it! You can check out their website, wiki and GIT sources:

The only thing that I’ve noticed missing in comparison to RHEV is the USB redirection drivers as so far they didn’t open sourced that… let’s wait for it 🙂

Deep dives RHEV3 GA

Per la gent que no es vulgui registrar us adjunto els pdf’s del deep dives que es varen publicar:

És molt interessant el roadmap per la versió del 3.1 on apareixeran noves funcionalitats que encara manquen la solució de RHEV comparant-la amb la de VMware vSphere.