XCP-ng 8.3 updates announcements and testing

olivierlambert

Hi,

We wrote some explanations in this blog post: https://xcp-ng.org/blog/2025/03/14/the-future-of-xcp-ng-lts/

Greg_E

@olivierlambert

So is that June 25, 2025 or 3 months from now as the drop dead date?

john205

@Greg_E neither. 8.2 is still LTS currently! They haven't switched it yet, but presumably it will be soon!

gduperrey

This will be three months after the official release of 8.3 LTS.

The release should take place in a few days when we release the ISO currently available for testing.

It's what is described in the "What to expect" part of the blogpost given above:

Guaranteed overlap period – There will be at least three months where both XCP-ng 8.2.1 and XCP-ng 8.3 LTS will be supported simultaneously, ensuring organizations can transition smoothly.

Greg_E

@gduperrey

OK, 3 months is good because I'm in a nasty bind right now and this may need to wait until August. I would expect many other places to have the same issues.

gb.123

This post is deleted!

olivierlambert

@gb.123 Hi, please open an issue on https://github.com/vatesfr/xen-orchestra/issues and ideally provide a screenshot or a detailed description of the problem. Thanks!

gb.123

@olivierlambert
Sure.

stormi

said in XCP-ng 8.3 updates announcements and testing:

here are the pre-release ISO images for a refreshed XCP-ng 8.3 installer

Last call

JeffBerntsen

@stormi I just used them to upgrade the 8.2.1 systems in my test pool. All seems fine so far.

ph7

@stormi
Did some minor testing and it seems to work fine

Andrew

@stormi I did a standalone host ISO install, all works as expected. I also did a pool ISO upgrade (8.2.1 to 8.3), master first, others second, migrated live VMs from old to new, all works as expected.

gb.123

@stormi

Did minor testing. Seems ok.
Haven't tested Backups.

Andrew

@stormi Upgrade problem... I upgraded a good working busy 8.2.1 server to 8.3 (using the new ISO). The upgrade went well without error. No guest VMs were changed.

Same issue in XO (Master 7be70) and XOA (5.107.2), so it must be an XCP issue. There are three new problems (all was working before);

XCP coretemp no longer loads/works. Error: coretemp coretemp.0: Adding Core 0 failed
XO Host CPU stats and Load are now reported as zero (It's a busy machine, they are not zero)
XO All guest VMs report zero CPU usage. Some just report No stats. for CPU. They do have current recognized guest tools (Linux and Windows). They do report other stats (memory, network, disk).

Other older XCP 8.3 hosts/guests are working.

stormi

@Andrew Does restarting the toolstack bring the stats back?

CC @Team-XAPI-Network

Regarding coretemp, @r1's module doesn't work anymore with Xen 4.17. See https://github.com/xcp-ng/xcp/issues/669. A possible workaround is using IPMI readings, when available. For a better solution, there's work needed in Xen.

(CC @Team-Hypervisor-Kernel, FYI)

Andrew

@stormi Got it... I missed that one for coretemp. Vates ticket opened for the XOA stats problem after 8.3 upgrade.

stormi

The above issue is solved in packages that we haven't released as an update yet, that @Andrew tested.

stormi

You probably saw it, but just in case: https://xcp-ng.org/blog/2025/06/16/xcp-ng-8-3-is-now-lts/

Today marks several important updates for XCP-ng 8.3. In a nutshell:

It officially becomes a Long-Term Support (LTS) release, as previously announced when it was first released on October 7th, 2024.

We are releasing updated installation images ("ISOs") that include installer improvements and all updates published since the original release.

XOSTOR, our hyperconverged storage solution powered by LINSTOR, is now officially supported on XCP-ng 8.3.

A new, dedicated upgrade ISO is available to support upgrading from an 8.2 pool that includes a XOSTOR storage repository.

JeffBerntsen

@stormi @olivierlambert I did see it! Contratulations and a huge thank you for the new LTS release!

gb.123

@stormi
Just for clarification sake (I know this might have been said before), installing patches is the same as upgrading from iso in this case ?
(Unlike with previous update where it was mandatory to upgrade using iso)