@RobWhalley I think in the beginning i had that option enabled in my backup jobs, but found it was a hassle to move VMs between hosts with it on so i turned it off for all backups. Might be why my jobs worked because i had already done that switch in the past.

posted in the other thread as well but Xen Orchestra, commit 1a7b5 backups are working again. I tested configure and vm backups. They are being backup to NFS share.

updated my two hosts without issues.

updated on my three servers no issues.

@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.

try downgrading your nfs to use version 3. I think version 4.x has performance issues.
in you settings-->remote, you can edit the nfs mount for backups and add in the -o options section.

I dont know the exact command but you can try using nfsvers=3 and see if that helps.

scratch that prior comment. My backups are all setup as delta backup with schedule 2nd run that forces full backup. So i believe both are working correctly.

if you can also try deleting all the backup snapshots of the VMs in the backup and running full backup then the delta backup jobs.

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

looks good
Xen Orchestra, commit 384bb
Master, commit 384bb

thanks for quick fix

@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?