Technology1 min read

How to run I/O workloads on OpenShift Virtualization VMs

By · Published by Everything Blog

In short

The test harness leverages virtctl ssh to access target virtual machines directly, eliminating the requirement for separate guest networking routes. It automates critical benchmarking lifecycle steps, including package installation, data pre-writing, execution, cleanup, and centralizing results into a single mounted directory. The setup supports Fedora, Red Hat Enterprise Linux, and CentOS-style distributions, which can benchmark either system drives or attached data disks. A bastion host equipped with Podman and cluster tools is necessary alongside dynamic storage to run these jobs.

Key points

  • Orchestration via environment variables and YAML files enables seamless integration into…: Orchestration via environment variables and YAML files enables seamless integration into automated continuous integration pipelines.
  • Engineers can benchmark either existing environments or trigger automated provisioning to…: Engineers can benchmark either existing environments or trigger automated provisioning to deploy fresh Linux guests during the run.
  • Successful deployment requires an operational OpenShift Virtualization cluster, dynamic s…: Successful deployment requires an operational OpenShift Virtualization cluster, dynamic storage classes, and a Podman-ready bastion host.

Sources checked by our analysis pipeline: 1

Editor's note

This post was originally published in October 2025 and has been updated to reflect the latest containerized FIO test harness and automated VM provisioning workflows.

Testing input/output (I/O) performance at scale presents challenges such as keeping track of test start and stop times, running tests against all hosts in parallel, and analyzing results across runs. This blog post shows how to run a generic Linux Flexible I/O Tester (FIO) workload against virtual machines (VMs) on Red Hat OpenShift Virtualization, using the current fio-container

harness.

From scattered SSH to 1 repeatable FIO run

The harness turns multi-VM FIO into a single, repeatable container run instead of hand-driven Secure Shell (SSH) sessions and ad hoc scripts. It runs the same FIO matrix across many OpenShift Virtualization guests in parallel, with coordinated start, wait, and result collection.

You configure once via YAML or environment variables, which fits both interactive lab use and Jenkins-style continuous integration (CI). Default access to virtual machines is via virtctl ssh

directly to VMs, so you don't need a separate guest network path for orchestration. Optional CREATE_VMS=true

Technology