How to install a foreign rpm package in RHEV6.2 Hypervisor?

Latest response



I have an RHEV6.2 hypervisor installed .I have an rpm kit which will be used to get the host HBA details.since hypervisor / is readonly if i want to install the package, is there a proper procedure available? 


# cat /etc/redhat-release

Red Hat Enterprise Virtualization Hypervisor release 6.2 (20120320.0.el6_2)







RHEV-H has no facility for installing additional software, it is an appliance and not a distribution. If you need to install extra software, you need to use RHEL.

If you need to use RHEV-H, and there is a piece of software that is available for RHEL and you need in RHEV-H, you can file an RFE, through a support ticket

Thanks Dan,

 if a default installed rpm is corrupted , do i need to reinstall hypervisor  through RHEV-M or is there a way to reinstall only the corrupted rpm file?



RHEV-H is easy to reinstall - only takes about 10-15 minutes.


However, what RPM is corrupted, and how to you know it is?

its not just corrupted file. since i have done default installation, ifi want to install some other rpm, can i install it through yum??



If you are requiring installing additional packages, it won't be RHEV-H anymore - you might want to use RHEL as a hypervisor (if you have extra subscriptions available).


RHEV-H is pretty much an appliance-like installation that shouldn't need any customization other than initial configuration:


Did you check out the RHEV-H Deployment Guide?


All the documentation can also be found at the following address:





Red Hat, Inc.

No, RHEV-H cannot be altered, besides the smal changes made to config text files. It is essentially a liveCD, all the partitions are in r/o mode. If you need to make changes on a hypervisor, you will have to use RHEL, not RHEV-H.


What exactly do you want to install, btw?

thanks for your response Andrius and Dan.

We have our own rpm tool to query the HBA and target details which i wanted to install on the hypervisor.

The same we provide to our customers.


I have a Query here:

when we want to upgrade hypervisor, does it internally makes the root to r/w and then does the upgrade???



If the tool is opensource and industry-standard, and if it exists for RHEL or for Fedora, you can file an RFE for its inclusion in RHEV-H through a support case.


To answer your question, when an upgrade happens, RHEV-H replaces all the partitions with new partitions containing new data, preserving only a small amount of host-specific information. Nothing is remounted in r/w mode

Correct on additional software in rhev-h.  It might help to think of RHEV-H as being like the firmware in a router (or other electronic device).  It's not designed to allow you to add additional software.  That's essentially what RHEV-H is doing.


As for upgrade, just to clarify on how it is done.  All configuration, logs, data, etc are preserved across the upgrade.  The only thing that changes is the base livecd image that is run at boot time.  That image is installed into the Root Partition.  The previous image is preserved in case the new image has a problem in the RootBackup partition.  The root filesystem is never mount read/write.

Thanks Dan and Michael.

Are there any support, or plans to support, adding RPMs to a custom RHEV-H installation CD that customer or vendor provides?


Some software a customer might want to add:

- Multipath softare (EMC PowerPath, Dell EqualLogic HIT Kit for Linux)

- Monitoring/Management agent (Dell OpenManage, Nagios Agents etc.)

- UPS Agent (Might be better to handle this via RHEV-M)

- Driver for unsupported hardware

Hi Harald,


There is work done upstream, which will end up in RHEV after testing and stabilization of course -


As for your specific requests, while the proprietary parts will probably be addressed by the plugin feature (and since RHEV relies heavily on device-mapper-multipath, other agents will either have to work underneath it or be avoided), anything opensource, and available for RHEL in the official channels, can be requested to be added into RHEV-H, as an RFE (that needs to be opened via a support ticket).

The same goes for drivers - if there is a driver that RHEL does not include, the normal process is to have the hardware vendor post the driver code upstream, and then it makes it into RHEL, and thus RHEV.


Hope this helps,