oVirt alternatives and similar tools
Based on the "Virtualization" category.
Alternatively, view oVirt alternatives based on common mentions on social networks and blogs.
Vagrant9.5 9.8 L2 oVirt VS VagrantVagrant is a tool for building and distributing development environments.
Packer9.1 9.6 oVirt VS PackerPacker is a tool for creating identical machine images for multiple platforms from a single source configuration.
QEMU8.9 10.0 L2 oVirt VS QEMUOfficial QEMU mirror. Please see http://wiki.qemu.org/Contribute/SubmitAPatch for how to submit changes to QEMU. Pull Requests are ignored. Please only use release tarballs from the QEMU website.
Otto7.5 1.1 oVirt VS OttoDevelopment and deployment system designed as the successor to Vagrant.
XenServer4.2 8.7 L2 oVirt VS XenServerXenCenter, the Windows management console for XenServer
Ganeti4.0 7.9 L2 oVirt VS GanetiGaneti is a virtual machine cluster management tool built on top of existing virtualization technologies such as Xen or KVM and other open source software.
OpenNodeBuilds open-source infrastructure management software and implements cloud systems.
XCP-ngBased on Citrix XenServer, XCP-ng is a fully open source virtualization platform.
KVMLinux kernel virtualization infrastructure.
Proxmox VEComplete open source virtualization management solution.
VirtualBoxVirtualization product from Oracle Corporation.
XenVirtual machine monitor for 32/64 bit Intel / AMD (IA 64) and PowerPC 970 architectures.
ConVirtProvides the core functionality for centrally managing your KVM or Xen virtualized environment.
Access the most powerful time series database as a service
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of oVirt or a related project?
Welcome to the oVirt website source repository. This repository contains the code and images for the website and documentation.
How to contribute
Please join us! All content on ovirt.org is community-driven, and we welcome contributions!
Found a bug or documentation issue?
To submit a bug or suggest a documentation fix/enhancement for a specific page, navigate to the page, and click "Report an issue on GitHub" in the page footer. If it is a more general problem, simply submit an issue here and provide as much detail as possible.
Edit the site
To edit a single page, navigate to the page, and click "Edit this page on GitHub" in the page footer. That will create a simple Pull Request where you can propose your changes.
You can also clone and fork the repository like any other GitHub project, if you are more comfortable with that. See [CONTRIBUTING.md](CONTRIBUTING.md) for instructions on building and testing the site locally.
See [MAINTAINING.md](MAINTAINING.md) for information about site maintainers.
See [README_ORGANIZATION.md](README_ORGANIZATION.md) for information about how the source code is organized.
Most of the website content is written in Markdown. For information on formatting Markdown, see Markdown Basics.
You can create a new file two ways:
From your local Git repo folder, navigate to the relevant directory, create a new text file and save it with the following naming convention:
From the GitHub repo, navigate to the relevant directory and click the New File button at the top-right corner of the pane.
After you submit a PR to the ovirt-site reposiory, automation will verify your submission. If no error is found you'll see a green symbol and a text saying "All checks have passed". You can inspect the generated website by downloading the site-without-markdown.zip file from the automation system. In order to do so, click on the "Checks" tab within your PR and then click on "Website Tests" link on the left bar. You can find "site-without-markdown" artifact at the bottom of the page.
Once downladed the zip file, in order to check how the website looks like you need to extract the archive and serve the extracted directory with a web server.
An easy way to do it is using python:
python3 -m http.server from the web site directory. This won't provide a full replica of what will happen on the real website
because there are a few redirects provided via
.htaccess that can be processed only using apache. If you can run an apache server on your system you can extract the
/var/www/html/ and serve it with your apache installation.
Still need help?
If you have any other questions, simply submit an issue here and provide as much detail as possible.