Alternate Installation Methods
For production installations, we recommend installing oVirt in the Self-Hosted Engine configuration. In this configuration, oVirt Engine and a Host are installed together with the Engine running as a Virtual Machine on that Host. This configuration is preferred because the Engine Virtual Machine will be highly available (once a second Host is added).
However, if you prefer to run the oVirt Engine standalone on physical hardware or another virtualization provider, you can install oVirt Engine and Nodes / Hosts separately.
oVirt 4.4.10 is intended for production use and is available for the following platforms:
- Red Hat Enterprise Linux 8.5 (or similar)
- CentOS Stream
- Red Hat Enterprise Linux 8.5 (or similar)
- oVirt Node (based on CentOS Stream)
- CentOS Stream
See the Release Notes for oVirt 4.4.10.
Install oVirt Engine using RPM
oVirt Engine is installed using RPM packages on a supported Enterprise Linux 8 distribution, such as CentOS Linux or Red Hat Enterprise Linux.
Users can also compile from source, using the guides found under the Developers section. This is not recommended unless you are a developer or need to customize the source code.
Important: You cannot skip a version when updating oVirt Engine. For example, if you are updating from 3.6 to 4.4, you first need to update to 4.0, then to 4.1, 4.2, 4.3 and finally to 4.4. (Host upgrades can use the oVirt Fast Forward Upgrade tool.) If you are updating from 4.3, please note you’ll need to migrate your engine from el7 to el8.
Upgrading from previous releases
For a standalone engine this means basically:
- backup engine data on 4.3.10 with:
engine-backup --scope=all --mode=backup --file=backup.bck --log=backuplog.log
- copy the backup to a safe location
- reinstall engine host with EL 8
- enable repos with:
dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
dnf update(reboot if needed)
- enable modules with:
dnf module enable -y javapackages-tools pki-deps postgresql:12 389-ds
- install engine rpms with:
dnf install ovirt-engine
- restore the engine data with:
engine-backup --mode=restore --file=backup.bck --log=restore.log --provision-db --provision-dwh-db --restore-permissions --provision-dwh-db
Red Hat Enterprise Linux, CentOS Linux
Enable the Base, Optional, and Extra repositories (Red Hat Enterprise Linux only):
# RHEL only -- they are enabled by default on CentOS and oVirt Node sudo subscription-manager repos --enable="rhel-8-for-x86_64-baseos-rpms" sudo subscription-manager repos --enable="rhel-8-for-x86_64-appstream-rpms" sudo subscription-manager repos --enable="ansible-2-for-rhel-8-x86_64-rpms" # RHEL beta releases only sudo subscription-manager repos --enable="rhel-8-for-x86_64-baseos-beta-rpms" sudo subscription-manager repos --enable="rhel-8-for-x86_64-appstream-beta-rpms"
Add the official oVirt repository.
sudo dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm sudo dnf module enable -y javapackages-tools pki-deps postgresql:12 389-ds
Install oVirt Engine.
sudo dnf install -y ovirt-engine
Set up oVirt Engine.
Follow the prompts to configure and install the Engine.
Once the installation completes, oVirt’s web UI management interface will start and the URL will be printed to the screen. Browse to this URL to begin using oVirt!
See Browsers Support for supported browsers.
Download oVirt Node or Setup Hosts
You must now install at least one Node or Host to act as hypervisors. Enterprise features like migration and high availability require more than one Host.
oVirt supports two types of Hosts:
Depending on your environment requirements, you may want to use only oVirt Nodes, only EL Hosts, or both.
Download oVirt Node
oVirt Node is a minimal operating system based on CentOS that is designed to provide a simple method for setting up a physical machine to act as a hypervisor in an oVirt environment.
Download the oVirt Node Installation ISO (current stable is oVirt Node 4.4 - Stable Release - Installation ISO)
Write the oVirt Node Installation ISO disk image to a USB, CD, or DVD.
Boot your physical machine from that media and install the oVirt Node minimal operating system.
Or Setup a Host
Instead of or in addition to oVirt Node, you can use a standard Enterprise Linux installation as a Host.
An Enterprise Linux Host (such as CentOS or RHEL), also known as an EL-based hypervisor or EL-based Host, is a standard basic installation of an Enterprise Linux operating system on a physical server upon which the hypervisor packages are installed.
Install one of the supported operating systems (CentOS, RHEL) on your Host and update it:
sudo dnf update -y # reboot if the kernel was updated
Add the official oVirt repository:
sudo dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
See Enterprise Linux Hosts for full installation instructions.
Attaching your Hosts
Once you have installed additional oVirt Nodes or EL Hosts, use the oVirt Administration Portal to add them to the Engine. Navigate to Compute → Hosts → New and enter the Host details. See Adding a Host to the oVirt Engine for detailed instructions.
oVirt uses a centralized storage system for Virtual Machine disk images, ISO files, and snapshots. Before you can install a Virtual Machine, storage must be attached.
Storage can be implemented using:
Network File System (NFS)
iSCSI (Internet Small Computer System Interface)
Local storage attached directly to the virtualization Hosts
Fibre Channel Protocol (FCP)
Parallel NFS (pNFS)
Other POSIX compliant file systems
Using the oVirt Administration Portal, navigate to Storage → Domains → New and enter the Storage details. See Configuring Storage and Storage Administration for guidance on configuring storage for your environment.
Install Virtual Machines
Once oVirt Engine is installed and you have added Hosts and configured storage, you can now install Virtual Machines!
See the Virtual Machine Management Guide for complete instructions.
For best Virtual Machine performance and accurate dashboard statistics, be sure to install the oVirt Guest Agent and Drivers for Linux [for Windows] in each Virtual Machine.
The following virtual machine guest operating systems are supported:
|Operating System||Architecture||SPICE support |
|Red Hat Enterprise Linux 3 - 6||32-bit, 64-bit||Yes|
|Red Hat Enterprise Linux 7+||64-bit||Yes|
|SUSE Linux Enterprise Server 10+ ||32-bit, 64-bit||No|
|Ubuntu 12.04 (Precise Pangolin LTS)+ ||32-bit, 64-bit||Yes|
|Windows XP Service Pack 3 and newer||32-bit||Yes|
|Windows 7||32-bit, 64-bit||Yes|
|Windows 8||32-bit, 64-bit||No|
|Windows Server 2003 Service Pack 2 and newer||32-bit, 64-bit||Yes|
|Windows Server 2008||32-bit, 64-bit||Yes|
|Windows Server 2008 R2||64-bit||Yes|
|Windows Server 2012 R2||64-bit||No|
|Windows Server 2016||64-bit||No|
 SPICE drivers (QXL) are not supplied by Red Hat. Distribution’s vendor may provide SPICE drivers.
 select Other Linux for the guest type in the user interface
 not tested recently (?)
The console is a graphical window that allows you to view and interact with the screen of a Virtual Machine. In oVirt, you can use a web-based console viewer or a desktop application (we recommend Virt Viewer). For Windows virtual machines, Remote Desktop Protocol is also available. See Installing Console Components, VNC Console Options, and and Browser Support for more information.
RPM Repositories and GPG keys
RPM repository for oVirt 4.4 - Latest stable release
See RPMs and GPG for older releases, nightlies, mirrors, and GPG keys.