The oVirt system test suit downloads a copy of the oVirt repo to the local host it is running on before installing oVirt and running the tests. It done to improve test performance and reliability. You could easily download a copy of the oVirt repo (or any other yum repo) by using the `reposync` tool from the `yum-utils` package. You'll need more then the oVirt repo for an offline installation though, because oVirt has dependencies that are pulled from the CentOS repos, as well as other repos such as Gluster. You can figure out which repos you need by looking at the repo configuration files installed by the ovirt-*release*.rpm package. Those files could be used directly as configuration files for reposync, but you might want to add `exclue` and `include` clauses to limit the amount of RPMs downloaded. oVirt certainly does not need the whole CentOS repo, for example, only a small portion of it. You could actually clone the oVirt system tests (OST) repo [1] and look at the reposync files there to get an idea what a reposync configuration file for oVirt should look like. Those files would not be suitable for direct production use though, because they are meant to sync the development versions of oVirt. Another approach you can consider is installing oVirt using ovirt-node and the hosted-engine appliance. That way you get ready-made machine images that contain everything you need without requiring access to package repositories. [1]: https://gerrit.ovirt.org/#/admin/projects/ovirt-system-tests On Thu, 20 Jun 2019 at 07:42, <siovelrm(a)gmail.com&gt; wrote: -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted