← ← Back to all products
oVirt
Active
Cloud & Platforms Latest Version: 4.5.7 Latest Release: Dec 17, 2025
oVirt is a free, open-source virtualization management platform for managing KVM-based virtual machines.
Versions
7
Latest Version
4.5.7
Active Support
1
EOL
6
Lifecycle Timeline
Today ↓
4.5
4.5
4.4
4.4
4.3
4.3
4.2
4.2
4.1
4.1
4.0
4.0
3.6
3.6
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 4.5 | Mar 16, 2022 | - | No | 4.5.7 | No | Active |
| 4.4 | May 6, 2020 | - | May 20, 2022 | 4.4.10.7 | No | EOL |
| 4.3 | Jan 22, 2019 | - | May 20, 2020 | 4.3.11.4 | No | EOL |
| 4.2 | Dec 4, 2017 | - | Feb 4, 2019 | 4.2.8.9 | No | EOL |
| 4.1 | Jan 12, 2017 | - | Dec 17, 2017 | 4.1.11.2 | No | EOL |
| 4.0 | May 31, 2016 | - | Jan 12, 2017 | 4.0.7.5 | No | EOL |
| 3.6 | Sep 25, 2015 | - | Jun 23, 2016 | 3.6.13.5 | No | EOL |
Frequently Asked Questions
Which versions of oVirt have reached end of life?
The following oVirt versions have reached end of life and no longer receive security updates: 4.4, 4.3, 4.2, 4.1, 4.0, 3.6. It is recommended to upgrade to a supported version.
Is it safe to continue using oVirt 4.4?
oVirt 4.4 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of oVirt?
The latest version of oVirt is 4.5.7, released in the 4.5 release cycle.
How many versions of oVirt are currently supported?
oVirt currently has 1 actively supported version(s): 4.5.
When does oVirt 4.5 reach end of life?
oVirt 4.5 does not have a specific end-of-life date announced yet.
What should I do when oVirt reaches end of life?
When a oVirt version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.