EOL.WikiEOL.Wiki
← ← Back to all products

XCP-ng

Active
Operating SystemsLatest Version: 8.3.0Latest Release: Aug 23, 2024

XCP-ng is a free, open-source virtualization platform based on XenServer/Citrix Hypervisor.

Support summary

XCP-ng currently has supported cycles. Track the next EOL date and validate upgrades before your change window.

What do EOL and support statuses mean?

Next EOL

Nov 30, 2028

XCP-ng 8.3 · 832 days left

Supported cycles

1

1 lts

Versions

7

Latest Version

8.3.0

Active Support

1

EOL

6

Lifecycle Timeline

Today
8.3
8.3
8.2
8.2
8.1
8.1
8.0
8.0
7.6
7.6
7.5
7.5
7.4
7.4
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
8.3Oct 7, 2024YesNov 30, 20288.3.0No
Active
8.2Nov 13, 2020NoJun 25, 20258.2.1
Yes
EOL
8.1Mar 31, 2020NoMar 31, 20218.1.0No
EOL
8.0Jul 25, 2019NoNov 13, 20208.0.0No
EOL
7.6Oct 31, 2018NoMar 30, 20207.6.0No
EOL
7.5Aug 10, 2018NoJul 25, 20197.5.0No
EOL
7.4Mar 31, 2018NoOct 31, 20187.4.0No
EOL

Data sources

Frequently Asked Questions

Which versions of XCP-ng have reached end of life?
The following XCP-ng versions have reached end of life and no longer receive security updates: 8.2, 8.1, 8.0, 7.6, 7.5, 7.4. It is recommended to upgrade to a supported version.
Is it safe to continue using XCP-ng 8.2?
XCP-ng 8.2 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 XCP-ng?
The latest version of XCP-ng is 8.3.0, released in the 8.3 release cycle.
How many versions of XCP-ng are currently supported?
XCP-ng currently has 1 actively supported version(s): 8.3.
When does XCP-ng 8.3 reach end of life?
XCP-ng 8.3 is scheduled to reach end of life on Nov 30, 2028.
What should I do when XCP-ng reaches end of life?
When a XCP-ng 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.