@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 - It was on, I toggled it off, re-ran the backup, still failed.

@ph7 that is a good news thank you for your patience and help

Great News!!

Ping @Team-Hypervisor-Kernel

@Danp Yes, they are all 'empty': xe vm-cd-list --multiple | grep -i false doesn't give any output.

Regarding the restore thing, it's clearly sub optimal, can you submit an improvement feedback directly to https://feedback.vates.tech?

@gduperrey Worked swell, thanks

@dinhngtu @teddyastie Do you have a time line / rough estimated release date regarding Rust-based xen-guest-agent version 1.0? Currently evaluating if I need to switch my Linux guests back to Citrix guest tools in the meantime. Looking forward to a reply. Thank you in advance.

@dinhngtu Yeah, I suspected that as well. So I inspected the SR and it showed connected to both hosts (at least in the XO UI - I didn't drop to the CLI to really confirm). By altering my workflow a bit and slowing down, I seem to have found the right "sweet spot" of delay and the issue hasn't resurfaced. Here's what I'm doing now, when I need to revert the snapshots of all three VMs: In the XO VM list, I select the three VMs and power them off at the same time. I then start with VM1 and eject the ISO, VM2 and eject the ISO, then VM3 and eject the ISO. By the time I circle back to VM1 for the next step, about 10-15 secs have elapsed. I then start with VM1 and revert the snapshot, and repeat the same on VM2 and VM3. By the time I circle back to VM1 for the next step, another 10-15 secs have elapsed. I re-attach the ISO to all three VMs in sequence. Another 10-15 secs elapse. I then start with VM1 and power all three VMs sequentially. The entire workflow takes about 30-45 secs, and I'm finding that by doing this, the issue hasn't resurfaced.

@nikade more beautiful than scary, it goes in an usual place where no one lives as you can see on satellite view it's an effusive éruption, not explosive, i was barely 100m when taking photos and you can also poke lava with a stick if you want (but need appropriate masks because of harming gazes like sulfur) not the first time it goes to the sea, the island expands slowly no casualties except from some fishes

@dinhngtu You rock - thank you!

@User-cxs You are probably experiencing this issue. Just a guess because you didn't actually ask a question.

@blueh2o Ooops, sorry - I read your message the wrong way around. You're right, that sounds really weird in your case....

@User-cxs si ici :[image: 1774010356739-c9d11a94-06d8-4a3c-b191-f95b2e2ef6f7-image.jpeg] tu DISABLE le serveur. tu nous confirme que c'est "comme" le probleme que tu constates ? un XOA tout vide en page d'accueil ? tu re ENABLE, et ça reviens ok ? tu n'as pas de probleme réseau / micro coupures / host distant au XOA (ipsec/openvpn?) ? la déco/reco que tu as me fait penser a un simple probleme réseau (si ça reviens tout seul et aucun autre impact...)

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