-
Home host, no XOSTOR, updated fine, no issue with my usual VMs.
-
Installed on my test server, not running XOSTOR, everything seems to be working fine so far.
-
Update published: https://xcp-ng.org/blog/2025/03/12/march-2025-security-and-maintenance-update-for-xcp-ng-8-2-lts/
Thank you for the tests!
-
New security update candidates for you to test!
Yet more vulnerabilities in Intel hardware, addressed in two complementary ways: patching Xen and updating Intel microcode.
Together with this security update, will also publish a patched XAPI to fix a minor issue with information reporting from VM to hypervisor.
Test on XCP-ng 8.2
From an up-to-date host:
yum clean metadata --enablerepo=xcp-ng-candidates yum update --enablerepo=xcp-ng-candidates reboot
The usual update rules apply: pool coordinator first, etc.
Versions
microcode_ctl
: 2.1-26.xs29.8.xcpng8.2 (weird identifier for historical reasons, but that's actually Intel microcode published by them yesterday)xen
: 4.13.5-9.49.1.xcpng8.2xapi
: 1.249.41-1.2.xcpng8.2
What to test
Normal use and anything else you want to test. The closer to your actual use of XCP-ng, the better.
Test window before official release of the updates
~24h. That's an urgent one.
-
Installed and seems to be running fine so far on my test systems.
-
@stormi I needed an excuse to reboot all my hosts... Upgraded and running on stable pools. I see the Intel 11th gen new microcode. All working normally at this time.
-
Update published: https://xcp-ng.org/blog/2025/05/14/may-2025-security-update-for-xcp-ng-8-2-8-3/
Thank your for the tests.
-
Updated our own prod via XO RPU, everything is working fine