@stormi Microcode updated on affected Gen11 i7. Running normally.

@gduperrey I jumped in all the way by mistake... I updated a wrong host, so I just did them all. Older AMD, Intel E3/E5, NUC11, etc. So far, so good. Add/migrate/backup/etc VMs are working as usual. Good for guest tools too, but mine are mostly Debian 7-11. Stuff is as usual so far.

I agree and I'll say it again, Thanks! It's not just Linux/Xen stuff. It is XCP-ng and XO that make everything work as a cohesive vertical open-source solution (some nice buzz words). Thanks to the Vates team and community that have built and support it. I look forward to ongoing continuous improvement and innovation!

@bleader Installed and running.

@bleader Updates running on several old and new intel machines (including microcode update). Working fine so far. Rolling Pool Reboot is a helpful feature.

@bleader I installed it on a bunch of busy hosts. All are fine, but none used PCI passthrough. The Rolling Pool Reboot in XO was very helpful.

@dinhngtu On a quick test, the ISO boots and installs. When the VM boots from the HD it crashes (and on reboots).

Updating XCP 8.3 with qemu-4.2.1-5.2.12.2~fixvwc1.1.xcpng8.3.x86_64 solves the issue and the installed windows image boots correctly without any additional changes.

@abudef @olivierlambert @thomas-dkmt I agree. I read block the same way... how about disable or prevent. (French? empêcher)

@julien-f @olivierlambert

Thanks for the ability to delete XO task logs feature! (XO commit f6e6e)

@gduperrey Installed and running on Intel systems, and Zen3 system that sees the microcode update.

@olivierlambert I would think HP servers would be a top tier for IPMI support.... please...

@gduperrey Up and working on several Intel pools.

@florent I updated XO to master 60ba5, and still having the issue.

I don't see any errors in the backup log. It just says "isFull": true for the ones stuck on full backups.

The XO log just reports:

Mar 24 16:26:47 xo1 xo-server[21199]: 2026-03-24T20:26:47.315Z xo:backups:worker INFO starting backup
Mar 24 16:26:52 xo1 xo-server[21199]: 2026-03-24T20:26:52.359Z xo:xapi:xapi-disks INFO export through vhd
Mar 24 16:26:54 xo1 xo-server[21199]: 2026-03-24T20:26:54.410Z xo:xapi:xapi-disks INFO export through vhd
Mar 24 16:29:22 xo1 xo-server[21199]: 2026-03-24T20:29:22.250Z xo:backups:worker INFO backup has ended

Note, it reports two export through vhd and does two full backups and one delta.

@acebmxer Yes, 22 or 24 should work correctly. Some early versions of 24 had issues, but not currently. I'm running 24 and it is working.

@florent I too am having issues with this... on some VMs...

Running XCP 8.3 (latest March update), XO (master 0286f).

I have a simple small CR job that replicates 3 VMs between two pools. Two VMs got stuck at Full, and one works correctly. CBT/NBD 1 enabled. Purge disabled.

It's also leaving snapshots each time. No CD in the drive this time.

I'll have to update XO and try again.

@acebmxer Use current Node LTS version... Currently 24.14.0
Or you can use 22.22.1.... use the latest version.

22.3 is the oldest version allowed to be supported (don't use one that old).

@florent I rebuilt my XCP hosting environment (everything is faster and bigger stuffed into one rack).... and this issue is now worse.

The main changes to this new setup are 2x40Gb networking, faster NFS NVMe NAS, faster pool servers, more memory, much faster CR destination machine with ZFS.

Running XCP 8.3 (March 2026 updates) and XO (master a2e33).

Replication is leaving many attached to control domain every day with NBD connection set to 2. Changing it to 1 seems to resolve the issue (no more stuck to control domain).

@yann Item Opened on Gitlab.

@olivierlambert Error causes tools to fail to load... >256 IP addresses on an interface (IPv4 and IPv6):

xen-guest-agent[514]: Error: Custom { kind: OutOfMemory, error: "no free slot for a new IP address" }

Best is to account for all the IP addresses.... second best is to ignore the extra IP addresses and not fail and exit.

@florent XO also can't migrate a VM to a new pool with a CD in the drive... It does generate an error, but the error is unclear.