went well with test systems. going to do prod soon.

i think im seeing the same with fake cpu spikes. I started a second pool yesterday to patch and left it on over night. typically i just shut it down once done so the servers dont get too far behind patching.
Under the pool stats im seeing spikes but under hosts nothing.
It doesnt really bother me, but figure i add to the thread that im also seeing it.

same with me and latest update

Same for me.

ill try to update manually and see if it changes.

Applied the latest pushed updated to production, no major issues.
The only thing to note is my backup XCP config failed Sunday, some time post the patches being applied. The error was the Body Timeout Error. This morning the backup ran without issues. Not sure why, but it wasn't a big deal and it working now. So not sure tied in with patching or not.

@MajorP93 said:

dmidecode -s system-product-name

that fixed it

i see the sensor info when i run ipmitool sensor on the server. So i took that info and put it into pluggin reg settings.

pluggin

my host shows OEM generic info as manufactor

So am I doing something wrong to get the general stuff working on asrock motherboard?

update to latest test patches on 2nd pool. no issue. LACP worked, started UB26 VM on host 4 and live migrated to host 3.

after i manually applied the patches, i used XO to reboot the host 2.
After the host 2 rebooted, XO still showed the task running and the host2 showed it needed to be patched. I rebooted XO and the task is still there ( been there for 13 hours now lol. ) but now host 2 shows patched

latest patches, host1 /master patches went well and rebooted. moved vms over.
host 2 in pool click on patch and it just sat there.

i ssh into the host2 yum clean metadata and yum update manually applied updates.
XO still showed host 2 needing patching, so i reboot it. XO still showed host 2 need patches.
I rebooted XO. host 2 shows patch, and task still remains in XO. Any idea how to clear it out from XO. or is it wait 24 hours kinds of thing?

@stormi said:

We pushed the updates to the xcp-ng-updates repository: https://xcp-ng.org/blog/2026/05/21/may-2026-updates-3-for-xcp-ng-8-3-lts/

Changed since the initial announcement, xen was updated with the proper vulnerability fix and an update to sm was added to fix an issue on LVM-based SRs with CBT enabled.

Thanks everyone for your feedback!

update main pool. so far so good. updates went well and vms are running.

@rzr said:

New security update candidates for XCP-ng 8.3 LTS (kernel, xen, intel-microcode)

i tested on one of my extra pools and so far i didnt see any issues. Grated i dont do much on that pool but i created a ubuntu 26 VM without issues.

Ill wait for full release to do my main pool.

@olivierlambert lol okay got it

@stormi I getting a response to reboot after applying to master.

anyone know if applying these two patches requires rebooting?

Just to add more data.
Xen Orchestra, commit 56b17
Master, commit 56b17
All patches on host are done.

the ipmitool works on my asrock MB but i dont see it in XO host screen.
I also didnt see it on xo6 interface.

yeah that was it, i removed the ip address from cfg file and it working now.

Updated to commit -db8ad this morning and backup is working.

I got back into v5 url once i removed LISTEN_ADDRESS="" from my xo-install.cfg

the backup ran on Xen Orchestra, commit cb85e

@florent I posted this in the v6 master thread, but it opens to the old interface but sits with a still loading message.