Tag Archives: rhev

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.: java.io.IOException: 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
engine-upgrade-check
yum update rhevm-setup -y
engine-setup
yum update rhevm-dwh rhevm-reports -y
engine-setup
yum update rhev-hypervisor6 -y

If upgrading rhevm-reports fails is due to this bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1086003

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
engine-setup

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/
 rhev-hypervisor.iso
 rhevh-6.2-20120209.0.el6_2.iso
 version-6.2-20120209.0.el6_2.txt
 rhev-hypervisor6.iso
 rhevh-latest-6.iso
 version.txt

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.

 

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):

system-config-authentication
  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:

/etc/samba/smb.conf 
/etc/krb5.conf 
/etc/resolv.conf

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
  ...
  level=DEBUG
  ...
service rhev-agentd restart
tail -f /var/log/rhev-agent/rhev-agent.log

oVirt

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 🙂