This developer documentation isoutdated, but provides historical context.

It isnotuser documentation and should not be treated as such.

Documentation is available here.

oVirt Test Day

oVirt 3.3 test day

oVirt 3.3 test day page

oVirt 3.2 test day


The purpose of test days initiative is to accomplish the following goals:

  • Get multiple engineers and stakeholders to have hands-on opportunity to learn more about Ovirt functionality and features.
  • Improve the quality of oVirt, towards its first release.
  • Establish a quality baseline.
  • Introducing and validating new oVirt 3.2 features
  • While learning about the project, the stakeholders can come with their own test cases, in different categories for regression testing:
    • installation/migration from 3.1
    • Storage
    • Networking
    • interfaces
    • Spice
    • User Interface
    • Tools

in addition participate in exploring new features .

What to do as a participant

  • If you already have the hardware, verify if it meets the hardware requirement, refer information detail section below
  • Update the Participants section.
  • Accomplish the goals set in objective section , run the tests, update the test matrix.
  • Running into any issues - contact any participant in the list


Test Days are open to anyone. If you have your own setup we will provide all the software packages and the required information. Please refer - What to do as a participant - in the section below, if you’re willing to participate please add yourself to the below table:

Name allInOne/distributed/migration from 3.1 Storage Networking APIs Spice User Interface Tools Distribution
mgoldboi clean install- AIO NFS basic + port mirroring python sdk V admin+user-portal   Fedora-18
lvernia - NFS everything - - webadmin   Fedora-17
danken - NFS rollback on setupNet error - - webadmin   el6
lhornyak - iscsi - - - webadmin   el6
apuimedo - NFS guest net operation, hotplugging nets and (if possible) live net change - - webadmin   el6
Gianluca - local and iSCSI basic - V webadmin + user portal   fedora 18
msalem - NFS network main tab - V webadmin   fedora 18
alkaplan - NFS network linking - - webadmin   fedora 18
sbonazzola Migration from 3.1 to 3.2 any basic process   - - setup/upgrade tools Fedora-17 and Fedora-18
dcaroest clean install-Distributed NFS basic process   - webadmin + user portal setup tools Fedora-18
knesenko tools NFS basic process   - webadmin setup tools Fedora-18
alourie clean install- AIO NFS basic + port mirroring python sdk       Fedora-18

Test Dates

The overall test dates are spread across multiple duration which are driven by the beta releases from the engineering. The following are the list of test days scheduled -

  • JAN 18th, 2012 - First Release (3.0)
  • Jun 14th, 2012 - Second Release (3.1)
  • JAN 31th, 2013 - Third Release (3.2)

Execution Plan and Guidelines

for installation check: Ovirt_Information_Details deployment options:

The following is the list of categories which we would like to focus on. this is basically regression testing:


You need at least two physical servers to install and configure a basic yet complete oVirt environment with shared storage to exercise the following:

Scenario Bugs
Setup oVirt engine using either Active Directory or Local IPA, two hosts configured as hypervisors (Fedora / Ovirt-Node / other) with power management (Storage Domains - Data Domain / ISO Domain and Export Domain)  
Setup oVirt engine - basic AIO flow 906544
Use ISO Uploader to populate images of OS and tools  
Basic Network Configuration  
Create virtual machines and assign them to users  
Migrate Virtual Machines between the hypervisors  
Collect log file using the log collector tool  
Upgrade from 3.1 to 3.2 including Fedora upgrade 906270


Scenario Bugs
Configure high availability for virtual machines which are running mission critical workloads, so they will be restarted on another host if hardware failure occurs  
Use the multi-level administration feature to assign different levels of user permissions  
Live Migration Scenarios  
Enable smartcard support for a VM and verify that the is passed to libvirt  


Scenario Bugs
Use the General configuration as a base configuration  
Create different types of storage domains (NFS, ISCSI, FC, local storage) with 2 or more data domains  
Install at least 2 VMs on each of the Data Centers  
Move the master domain to a different domain within the Data Center  
Export one of the installed VMs, delete it, import it to another Data Center  
Create a template from one of the VMs and then create a new VM based on this template  
Move the newly created VM to another data domain  
Create several snapshots from a VM (Each time change something in the guest)  
Create several live snapshots from a VM (Each time change something in the guest)  
Restore a previous snapshot  
Live migrate a disk between storage domains  
Storage Failovers  
Host Failovers  
Power User Portal provides power users the ability to create and manage virtual machines from the power user portal  
High Availability scenarios provides instructions to configure virtual machine and host high availability  


  • Base config - single NIC, bridge on top, VMs attached to NIC
  • Advanced configurations:

make sure each of the configs can:

  • survive a reboot
  • test network at both host and VM level
  • ping and transfer large amounts of data (2Gb size files should be enough)
  • remain operational over time (1hr of uptime should be sufficient for the basic testing)

Bugs found:

  • Bug 906289 - [oVirt-webadmin] [network] Non-VM networks shown as VM networks on cluster attachment dialog
  • Bug 906291 - [oVirt-webadmin] [network] Non-VM networks not being detached from cluster
  • Bug 906313 - [oVirt-webadmin] [setupNetworks] “No valid Operation for and Unassigned Logical Networks panel"
  • Bug 906383 - [vdsm] [setupNetworks] Error while attaching non-VM network to interface on Fedora 18
  • Bug 906393 - [oVirt] [network] Audit log message for unmanaged network
  • Bug 906394 - [oVirt-webadmin] [network] Loading animation in network main tab ‘hosts’ and ‘vms’ subtab is stuck on first view of the sub tab
  • Bug 906405 - Bad Error Message when Removing vNic from Running VM
  • Bug 906434 - Editing vnic’s type and mac are blocked when the vnic was unplugged and updated to plugged
  • Bug 906440 - Updating type of a plugged nic should be blocked on the ui side


  • Basic operations on iso-uploader:
  1. engine-iso-uploader list
  2. **engine-iso-uploader upload -i -v -f**
  • Basic operations on log-collector:
  1. engine-log-collector list
  2. engine-log-collector collect
  • Basic operation on image-uploader

**engine-image-uploader –name= -e upload my.ovf**

New to v3.1:

  • port mirroring: one can setup a VM that sniffs all IP traffic between VMs on a network on a host.
  • no mac spoofing: VMs cannot emit packets with spoofed mac address (unless specifically allowed to).
  • Sync network: change network MTU (or other property) on host, verify that Engine may overwrite it with Sync network
  • Jumbo packets: see if can be configured and used by storage

New to v3.2:

  • Network main tab operational: you can search hosts and VM based on their network connectivity
  • Guest agent reported devices: install guest agent on a VM and see it report internal information of the vNics (internal device name, IPv4 and IPv6)
  • Network Linking: allow changing network the VM is connect to while it is running


by default we’ll be using the webadmin as our API for testing on this section we’ll try to have default deployment with the different APIs

Scenario Webadmin UserPortal Rest Python-SDK CLI
Create a data-center          
Create a cluster          
Update cluster          
Install a host          
Create a storage domain on DC          
Attach export/ISO domain to DC          
Create vm          
Delete vm          
Import vm          
Start/hibernate/resume/stop vm          
Create a snapshot to vm          
Create a template from vm          
Create vm from template          
Sign out          

Python API of the above scenarios can be found in: Testing/PythonApi


For details about configuration check Testing/Spice

Scenario Bugs
Install Windows VM and a Linux VM with Guest Tools (QXL graphic driver and spice vdagent)  
Assign user to these vms, login to a user portal, from your client machine, and connect to it using the Spice protocol  
Try to watch a clip via YouTube or any other web based video (with QXL driver installed on VM)  
Try to watch a Local movie (with QXL driver installed on VM)  
Try to use client mouse mode and clipboard share between client and VM (with spice agent installed on VM)  
Install AutoCAD or any other graphic application a try to work with it (with QXL driver installed on VM)  

User Interface



oVirt Node image is not currently available for the Test Day. The image should be available within the next day or two.


Scenario Bugs
Set DC Quota enforcement mode to ‘Enforced’  
Create new Quota which limits storage  
Create new Quota which limits cpu and memory  
Define consumers for the quotas  
Asign the quotas to VMs and Disks  
Run VM with quota  
Move a disk  
Snapshot a vm (disk)  
Stop VM  
Commit snapshot  
See that quota usage makes sance  
Open User Portal  
Log-in as a user defined as quota consumer  
Create VMs and Disks  
Run VMs  
Go to resources tab and see that quota usage makes sance  

oVirt Information Details

Beta RPMs for Fedora 18 are available from In order to use it create a /etc/yum.repos.d/ovirt-engine-beta.repo file with the following content:


The run yum install ovirt-engine.

Please refer the following documents for more information on hardware requirements, installation procedure and software download locations:

Please refer the following documents for Ovirt Installation guide, bits location and admin guide:

Please refer the following document for ‘virt-to-date’ tool, simple tool for setting up local yum repo with all required packages and easy deployment.

In case you would like to test a product with a new test case, there is a template to be used for creating test cases. Please copy this template for the test case, and update the link in this document to point to the results table below. It is not necessary that the person who is writing the test case will also be the person executing the test case, please make sure the instructions are explicit enough that anyone who may want to participate in the test day can follow them, and execute it.

Bug Reporting

Tracker bug for the release -


IRC - #ovirt at

Current Issues