XCP-ng 8.3 updates announcements and testing
-
Big update...
Installed on Intel 13th gen and 14gen cpusCBT was already enabled on vms prior to update.
2026-11-19T19_42_40.762Z - backup NG.json.txt - After update - regular incremental backup2026-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.
-
@vxgmichel Applied and working on my test hosts. ssh-copy-id and connections via key worked without problems
-
@vxgmichel
Removed theauthorized_keys, rebooted, sent a newssh-copy-id root@<ip>
And I succeeded tosshin again
-
Testing/Tested on 2 pools
old-xcp-dev: 3 host HA
Dell Inc., (,PowerEdge R350,) Intel
Multipath enablednew-xcp-dev: 2 host
Dell Inc., (,PowerEdge R650xs,) Intel
Multipath enabledThe follwing tests haven't shown problems:
Backups with Healthchecks.
Live migrations inside pool.
Migrations between pools. Both forced and non-forced.
Reclaim space on primary SR -
@vxgmichel Installed on LAB and internal pools, so far no issues. We got hit by the broken CBT chain issue (https://github.com/xcp-ng/sm/pull/187) and we already patched this particular bug ourselves about 2 weeks ago. Since then, all delta backups run w/o issues and we also stress-tested one host (running many delta-backup jobs of the same VMs using different patterns, incl. parallel execution), again no issues.
-
Installed on my usual test pool.
Set disks of a FreeBSD VM to CBT. Migrated the VM from NFS to iSCSI storage. Started Delta Backup Job.
No issues except the backup was a full backup for this VM instead of a delta.
Followed up with a second backup which then was a delta backup again. No issues with either backup. -
@bufanda The CBT issue was only with file-based SR (like local ext od NFS). iscsi is block-based and was not affected. full run of delta-backup job after VDI migration to another SR is expected (cbtlog is not migrated and reference to former backup is lost).
-
-
This post is deleted! -
@vxgmichel @lmolina Pools updated, working so far. Rolling reboot failed because of backup (CR) conflicts. CR backups cause RPU to fail. RPU causes CR backups to fail.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login