Finally just finished our migration from VMware to XCP-NG.
VMs - 34 mix windows server and ubuntu linux.
Pools - 3
Host - 6
Dell R660 - 2
Dell R640 - 4

Finally just finished our migration from VMware to XCP-NG.
VMs - 34 mix windows server and ubuntu linux.
Pools - 3
Host - 6
Dell R660 - 2
Dell R640 - 4

Big update...
Installed on Intel 13th gen and 14gen cpus
CBT was already enabled on vms prior to update.
2026-11-19T19_42_40.762Z - backup NG.json.txt - After update - regular incremental backup
2026-11-19T19_46_25.835Z - backup NG.json.txt Migrated 1 vm from nvme SR QCOW2 format to hdd SR QCOW2 format and did another incremental backup.
installed no issues to report. Cold booted windows 11 vm and linux vm. Backup job ran also with no issues.
Running transaction
Updating : kernel-4.19.19-8.0.49.3.xcpng8.3.x86_64 1/2
Cleanup : kernel-4.19.19-8.0.46.14.xcpng8.3.x86_64 2/2
Verifying : kernel-4.19.19-8.0.49.3.xcpng8.3.x86_64 1/2
Verifying : kernel-4.19.19-8.0.46.14.xcpng8.3.x86_64 2/2
installed updates no issues.... shutdown and cold booted windows 11 vm and a few linux vms no issues found.
Update - Applying the linux kernel update to work hosts now. The host 1 in Tilton pool took about 5 min to reconnect to xoa/xoproxy after console showed host booted. Host 2 swapped vms and started its update and rebooted. It took about 1-2 min to reconnect.
Host 1 does show more output prior to the console fully loading then compared to host 2. I did not get a picture of the output. When I can reboot host again will try to catch the output.
Installed patches on home lab. No initial issues found. Existing Windows 11 vm no issues with it on basic vm functions. Created new Windows 11 vm with 26h2 iso no issues. Also installed guest tools in both vms.

Installed...
Updated:
blktap.x86_64 0:3.55.5-9.4.xcpng8.3 forkexecd.x86_64 0:26.1.16-1.2.xcpng8.3
message-switch.x86_64 0:26.1.16-1.2.xcpng8.3 qcow-stream-tool.x86_64 0:26.1.16-1.2.xcpng8.3
rrdd-plugins.x86_64 0:26.1.16-1.2.xcpng8.3 sm.x86_64 0:3.2.12-23.5.xcpng8.3
sm-cli.x86_64 0:26.1.16-1.2.xcpng8.3 sm-fairlock.x86_64 0:3.2.12-23.5.xcpng8.3
squeezed.x86_64 0:26.1.16-1.2.xcpng8.3 varstored-guard.x86_64 0:26.1.16-1.2.xcpng8.3
vhd-tool.x86_64 0:26.1.16-1.2.xcpng8.3 wsproxy.x86_64 0:26.1.16-1.2.xcpng8.3
xapi-core.x86_64 0:26.1.16-1.2.xcpng8.3 xapi-nbd.x86_64 0:26.1.16-1.2.xcpng8.3
xapi-rrd2csv.x86_64 0:26.1.16-1.2.xcpng8.3 xapi-storage-script.x86_64 0:26.1.16-1.2.xcpng8.3
xapi-tests.x86_64 0:26.1.16-1.2.xcpng8.3 xapi-xe.x86_64 0:26.1.16-1.2.xcpng8.3
xcp-networkd.x86_64 0:26.1.16-1.2.xcpng8.3 xcp-rrdd.x86_64 0:26.1.16-1.2.xcpng8.3
xenopsd.x86_64 0:26.1.16-1.2.xcpng8.3 xenopsd-cli.x86_64 0:26.1.16-1.2.xcpng8.3
xenopsd-xc.x86_64 0:26.1.16-1.2.xcpng8.3
We pushed the tested packages along a xen security update to the xcp-ng-updates repository, check blog post for summary and related advisories:
https://xcp-ng.org/blog/2026/07/28/july-2026-updates-1-for-xcp-ng-8-3-lts/
Just updated my homelab hosts.
[10:45 xcp-ng-disjqdnc ~]# yum clean metadata
Loaded plugins: fastestmirror
Cleaning repos: xcp-ng-base xcp-ng-updates
6 metadata files removed
4 sqlite files removed
0 metadata files removed
[10:45 xcp-ng-disjqdnc ~]# yum update
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Excluding mirror: updates.xcp-ng.org
* xcp-ng-base: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
* xcp-ng-updates: mirrors.xcp-ng.org
xcp-ng-base/signature | 473 B 00:00:00
xcp-ng-base/signature | 3.0 kB 00:00:00 !!!
xcp-ng-updates/signature | 473 B 00:00:00
xcp-ng-updates/signature | 3.0 kB 00:00:00 !!!
(1/2): xcp-ng-base/primary_db | 3.9 MB 00:00:00
(2/2): xcp-ng-updates/primary_db | 1.6 MB 00:00:01
Resolving Dependencies
--> Running transaction check
---> Package xen-dom0-libs.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated
---> Package xen-dom0-libs.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update
---> Package xen-dom0-tools.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated
---> Package xen-dom0-tools.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update
---> Package xen-hypervisor.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated
---> Package xen-hypervisor.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update
---> Package xen-libs.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated
---> Package xen-libs.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update
---> Package xen-tools.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated
---> Package xen-tools.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update
--> Finished Dependency Resolution
Dependencies Resolved
============================================================================================================================================
Package Arch Version Repository Size
============================================================================================================================================
Updating:
xen-dom0-libs x86_64 4.17.6-9.3.1.xcpng8.3 xcp-ng-updates 704 k
xen-dom0-tools x86_64 4.17.6-9.3.1.xcpng8.3 xcp-ng-updates 2.0 M
xen-hypervisor x86_64 4.17.6-9.3.1.xcpng8.3 xcp-ng-updates 2.4 M
xen-libs x86_64 4.17.6-9.3.1.xcpng8.3 xcp-ng-updates 66 k
xen-tools x86_64 4.17.6-9.3.1.xcpng8.3 xcp-ng-updates 47 k
Transaction Summary
============================================================================================================================================
Upgrade 5 Packages
Total download size: 5.2 M
Is this ok [y/d/N]: y
Downloading packages:
Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
(1/5): xen-dom0-tools-4.17.6-9.3.1.xcpng8.3.x86_64.rpm | 2.0 MB 00:00:00
(2/5): xen-dom0-libs-4.17.6-9.3.1.xcpng8.3.x86_64.rpm | 704 kB 00:00:00
(3/5): xen-libs-4.17.6-9.3.1.xcpng8.3.x86_64.rpm | 66 kB 00:00:00
(4/5): xen-hypervisor-4.17.6-9.3.1.xcpng8.3.x86_64.rpm | 2.4 MB 00:00:00
(5/5): xen-tools-4.17.6-9.3.1.xcpng8.3.x86_64.rpm | 47 kB 00:00:00
--------------------------------------------------------------------------------------------------------------------------------------------
Total 2.9 MB/s | 5.2 MB 00:00:01
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Updating : xen-libs-4.17.6-9.3.1.xcpng8.3.x86_64 1/10
Updating : xen-hypervisor-4.17.6-9.3.1.xcpng8.3.x86_64 2/10
Updating : xen-dom0-libs-4.17.6-9.3.1.xcpng8.3.x86_64 3/10
Updating : xen-tools-4.17.6-9.3.1.xcpng8.3.x86_64 4/10
Updating : xen-dom0-tools-4.17.6-9.3.1.xcpng8.3.x86_64 5/10
Cleanup : xen-dom0-tools-4.17.6-9.3.xcpng8.3.x86_64 6/10
Cleanup : xen-tools-4.17.6-9.3.xcpng8.3.x86_64 7/10
Cleanup : xen-dom0-libs-4.17.6-9.3.xcpng8.3.x86_64 8/10
Cleanup : xen-hypervisor-4.17.6-9.3.xcpng8.3.x86_64 9/10
Cleanup : xen-libs-4.17.6-9.3.xcpng8.3.x86_64 10/10
Verifying : xen-dom0-tools-4.17.6-9.3.1.xcpng8.3.x86_64 1/10
Verifying : xen-dom0-libs-4.17.6-9.3.1.xcpng8.3.x86_64 2/10
Verifying : xen-hypervisor-4.17.6-9.3.1.xcpng8.3.x86_64 3/10
Verifying : xen-libs-4.17.6-9.3.1.xcpng8.3.x86_64 4/10
Verifying : xen-tools-4.17.6-9.3.1.xcpng8.3.x86_64 5/10
Verifying : xen-libs-4.17.6-9.3.xcpng8.3.x86_64 6/10
Verifying : xen-dom0-tools-4.17.6-9.3.xcpng8.3.x86_64 7/10
Verifying : xen-hypervisor-4.17.6-9.3.xcpng8.3.x86_64 8/10
Verifying : xen-tools-4.17.6-9.3.xcpng8.3.x86_64 9/10
Verifying : xen-dom0-libs-4.17.6-9.3.xcpng8.3.x86_64 10/10
Updated:
xen-dom0-libs.x86_64 0:4.17.6-9.3.1.xcpng8.3 xen-dom0-tools.x86_64 0:4.17.6-9.3.1.xcpng8.3 xen-hypervisor.x86_64 0:4.17.6-9.3.1.xcpng8.3
xen-libs.x86_64 0:4.17.6-9.3.1.xcpng8.3 xen-tools.x86_64 0:4.17.6-9.3.1.xcpng8.3
Updates applied...
Updated:
forkexecd.x86_64 0:26.1.11-1.2.xcpng8.3 kexec-tools.x86_64 1:2.0.15-21.1.xcpng8.3
message-switch.x86_64 0:26.1.11-1.2.xcpng8.3 qcow-stream-tool.x86_64 0:26.1.11-1.2.xcpng8.3
rrdd-plugins.x86_64 0:26.1.11-1.2.xcpng8.3 sm-cli.x86_64 0:26.1.11-1.2.xcpng8.3
squeezed.x86_64 0:26.1.11-1.2.xcpng8.3 varstored-guard.x86_64 0:26.1.11-1.2.xcpng8.3
vhd-tool.x86_64 0:26.1.11-1.2.xcpng8.3 wsproxy.x86_64 0:26.1.11-1.2.xcpng8.3
xapi-core.x86_64 0:26.1.11-1.2.xcpng8.3 xapi-nbd.x86_64 0:26.1.11-1.2.xcpng8.3
xapi-rrd2csv.x86_64 0:26.1.11-1.2.xcpng8.3 xapi-storage-script.x86_64 0:26.1.11-1.2.xcpng8.3
xapi-tests.x86_64 0:26.1.11-1.2.xcpng8.3 xapi-xe.x86_64 0:26.1.11-1.2.xcpng8.3
xcp-networkd.x86_64 0:26.1.11-1.2.xcpng8.3 xcp-rrdd.x86_64 0:26.1.11-1.2.xcpng8.3
xenopsd.x86_64 0:26.1.11-1.2.xcpng8.3 xenopsd-cli.x86_64 0:26.1.11-1.2.xcpng8.3
xenopsd-xc.x86_64 0:26.1.11-1.2.xcpng8.3
Complete!
Will continue to test.
@rzr Installed latest update and no issues to report. I dont hvae any 2tb+ drives in my vms. converting from vhd to qcow2 and backups all working.
installed updates will report back.
Update - I had migrated vms back over to vhd prior to update release. I have migrated 2 vms back over to qcow2 and the initial backup ran successfull. Ran a second delta backup and that as well was successful with out issues. Backups happen very quickly now. But it appears the % and progress bar are working.
When CBT is enabled on the vm vdi. They show up as needing to be coalesced. VMs without CBT enabled the vdis are coalesced.

Will continue to monitor.
Once the coalesence hits 2 for the vm. The vm is skipped form future backups until cleared. (shutting down the vm will allow the coalescence to happen.
2026-04-23T19_52_34.694Z - backup NG.txt


Big update...
Installed on Intel 13th gen and 14gen cpus
CBT was already enabled on vms prior to update.
2026-11-19T19_42_40.762Z - backup NG.json.txt - After update - regular incremental backup
2026-11-19T19_46_25.835Z - backup NG.json.txt Migrated 1 vm from nvme SR QCOW2 format to hdd SR QCOW2 format and did another incremental backup.
Thank you both for the reply's, I look forward to the upcoming changes.
So when you used my script it worked aside from the backup hiccup? My script for the node version I added the ability to choose a node version or stick to LTS releases. If that helps you pin down the node version issue. When switching use the --rebuild option to rebuild xo on the new version. Otherwise if there are xo updates it will upgrade node if change or new LTS. It should downgrade but not tested safe to use the rebuild to make the change.
Now that there is more progress in v6 specifically in the backup section. Not sure if this is a bug or as intended, leaning towards a bug.
This is my existing backup job that works just fine in v5 with sequences task setup. The below recommendation would that create two separate backup chains, one of deltas, and one of full backups? Also it will not let me to manually run the backup job as it states the job has more then one schedule.
Node - v26.13.1
Commit - 3cd44



I have asked multiple times in the past about what version of Node.js should be. While using the latest LTS version was stated documentation keep using Node.js 22 in the examples. I do believe XOA is lacking on the latest LTS version last i looked into it. I think this is what may be causing the confusion.
So have disabled the synology device from the remotes page.

I then logged into the synology device and did a normal shutdown. (had maintenance work to do anyway). So far the synology device has been powered off for going on 30 min and XO is still responding just fine. So far the only thing i am seeing is you can not see the backups / restore points as the remote is offline. (expected) Will keep it off and see when it stops (if it stops responding). I did migrate xo and it stayed up. I can try a reboot and / or apply the latest commits while the synology device is off.
While discussing this with Claude as I was having issues seeing the obvious. That disabling the remote(s) xo does not unmount the remote(s) all the time... As shown above I have two remotes that are disabled and one remote is still mounted, shown below. Also not knowing the need to disable the remote before it goes offline or when an unexpected outage occurs.
This is also possibly what I ran into last time and didnt bother to follow up with about it.
❯ findmnt -t nfs,nfs4
TARGET SOURCE FSTYPE OPTIONS
/run/xo-server/mounts/2ab02323-0d47-43a5-9081-b2454e036c70
10.100.2.23:/volume1/backup
nfs4 rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=
Update: I re-tested with the Synology powered on the whole time. I enabled both remotes, then disabled both. Both are still mounted:
❯ findmnt -t nfs,nfs4
TARGET SOURCE FSTYPE OPTIONS
/run/xo-server/mounts/2ab02323-0d47-43a5-9081-b2454e036c70
10.100.2.23:/volume1/backup
nfs4 rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,s
/run/xo-server/mounts/588145e7-1e41-4e61-a717-c0b4cce7646a
10.100.253.23:/volume1/Backups
nfs4 rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,s
xo-server still has files open on both mounts (deleted keeper files, renamed .nfs… by NFS), which keeps them busy so they can't be unmounted:
❯ sudo ls -l /proc/$(systemctl show -p MainPID --value xo-server)/fd | grep xo-server/mounts
l-wx------ 1 root root 64 Nov 12 22:15 30 -> /run/xo-server/mounts/2ab02323-0d47-43a5-9081-b2454e036c70/.nfs000000000000443400000005
l-wx------ 1 root root 64 Nov 12 22:15 34 -> /run/xo-server/mounts/2ab02323-0d47-43a5-9081-b2454e036c70/.nfs000000000000443e00000009
l-wx------ 1 root root 64 Nov 12 22:15 36 -> /run/xo-server/mounts/2ab02323-0d47-43a5-9081-b2454e036c70/.nfs000000000000443d00000008
l-wx------ 1 root root 64 Nov 12 22:15 39 -> /run/xo-server/mounts/588145e7-1e41-4e61-a717-c0b4cce7646a/.nfs00000000000036b70000000b
l-wx------ 1 root root 64 Nov 12 22:15 40 -> /run/xo-server/mounts/588145e7-1e41-4e61-a717-c0b4cce7646a/.nfs00000000000036b80000000c
XO from sources, commit 67ed8f7eb (2026-11-12), Node v26.13.0, Debian 13 (trixie).
just to confirm you are disabling the Backup NFS SR? Before it goes off line? I can try this again in my setup just not sure if i still kept the script i created that the synology would used to send the disable the remote before shutdown.
=======================================================================================================================================================
Package Arch Version Repository Size
=======================================================================================================================================================
Downgrading:
kernel x86_64 4.19.19-8.0.46.16.xcpng8.3 xcp-ng-updates 29 M
Transaction Summary
=======================================================================================================================================================
Downgrade 1 Package
Total download size: 29 M
Is this ok [y/d/N]: y
Downloading packages:
kernel-4.19.19-8.0.46.16.xcpng8.3.x86_64.rpm | 29 MB 00:00:07
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : kernel-4.19.19-8.0.46.16.xcpng8.3.x86_64 1/2
depmod: WARNING: /lib/modules/4.19.0+1/kernel/crypto/authencesn.ko needs unknown symbol memcpy_sglist
Cleanup : kernel-4.19.19-8.0.49.3.xcpng8.3.x86_64 2/2
Verifying : kernel-4.19.19-8.0.46.16.xcpng8.3.x86_64 1/2
Verifying : kernel-4.19.19-8.0.49.3.xcpng8.3.x86_64 2/2
Removed:
kernel.x86_64 0:4.19.19-8.0.49.3.xcpng8.3
Installed:
kernel.x86_64 0:4.19.19-8.0.46.16.xcpng8.3
Updated:
forkexecd.x86_64 0:26.1.21-1.4.xcpng8.3 message-switch.x86_64 0:26.1.21-1.4.xcpng8.3 qcow-stream-tool.x86_64 0:26.1.21-1.4.xcpng8.3
rrdd-plugins.x86_64 0:26.1.21-1.4.xcpng8.3 sm-cli.x86_64 0:26.1.21-1.4.xcpng8.3 squeezed.x86_64 0:26.1.21-1.4.xcpng8.3
varstored-guard.x86_64 0:26.1.21-1.4.xcpng8.3 vhd-tool.x86_64 0:26.1.21-1.4.xcpng8.3 wsproxy.x86_64 0:26.1.21-1.4.xcpng8.3
xapi-core.x86_64 0:26.1.21-1.4.xcpng8.3 xapi-nbd.x86_64 0:26.1.21-1.4.xcpng8.3 xapi-rrd2csv.x86_64 0:26.1.21-1.4.xcpng8.3
xapi-storage-script.x86_64 0:26.1.21-1.4.xcpng8.3 xapi-tests.x86_64 0:26.1.21-1.4.xcpng8.3 xapi-xe.x86_64 0:26.1.21-1.4.xcpng8.3
xcp-networkd.x86_64 0:26.1.21-1.4.xcpng8.3 xcp-rrdd.x86_64 0:26.1.21-1.4.xcpng8.3 xenopsd.x86_64 0:26.1.21-1.4.xcpng8.3
xenopsd-cli.x86_64 0:26.1.21-1.4.xcpng8.3 xenopsd-xc.x86_64 0:26.1.21-1.4.xcpng8.3
Complete!
Not spinning, but the backups tab is gone, It was really only good to see the green check marks or red x, but gone as of the update I did about 24 hours.
I didnt notice the backup tab missing at first but also for me.
Edit - Found
