@Kraken89 I will look into the transition from the previous system to the new one maybe that's the key

Not yet, I think it's already planned, check https://feedback.vates.tech

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

I am on it , thanks for all the informations

@JSylvia007 Error: stream has ended with not enough data (actual: 397, expected: 2097152) is the root cause, can you post the json here ? remove the snapshot on the source to start a new backup chain .

https://github.com/acebmxer/install_xen_orchestra Made some improvements to the script including a inter active menu that will show commit for the script itself compared to the master commit. (should relected which branch you run the script from) With Xen Orchestra Commit comparison and show the Node version installed. The script should self update on launch. Always review code before using. Use in production at your own risk. Always open to ideas and suggestions. ╔══════════════════════════════════════════════════════════════════════════════════╗ ║ Install Xen Orchestra from Sources Setup and Update ║ ╚══════════════════════════════════════════════════════════════════════════════════╝ Current Script Commit : 693f4 Master Script Commit : 693f4 Current XO Commit : a1b2c Master XO Commit : d4e5f Current Node : v24.1.0 ────────────────────────────────────────────────────────────────────────────────── ▸ [✓] Install Xen Orchestra [ ] Reconfigure Xen Orchestra [ ] Update Xen Orchestra [ ] Rebuild Xen Orchestra [ ] Rename Sample-xo-config.cfg [ ] Edit xo-config.cfg [ ] Install XO Proxy ────────────────────────────────────────────────────────────────────────────────── Selected: 1 ↑↓←→ Navigate SPACE Select/Deselect ENTER Confirm Q Quit

UPDATE: its been 2 days and as I suspected the VDI is still waiting to coalesce at a length of 1, The GC does not seem to be cleaning it up. Does anyone have suggestions for how to remove this orphaned VDI and base copy. I'm not interested in saving the VM just cleaning up the remnants of the botched migration and removal.

I am trying to setup the same VxLAN Private Network between two pools. I have been running XO from sources (commit 813514821) for a while now and encountered the same error "No PIF found in center". Therefore I updated to the latest commit 60ba5070c (still using XO v5) and now I was able to create a VxLAN private network that spans two pools without an error. I checked the networks for both pools and noticed that two networks were created per pool, so I was able to create it despite the error from the older XO version. However, using either VxLAN to connect two VMs in different pools doesn't work. Pinging a VM over that VxLAN in the same pool and host works, but pinging a VM from another Pool doesn't work. This is also the case when using GRE, Looking at the ARP Table, it seems that the VMs from different pool do show up, but as incomplete: [image: 1774432891674-screenshot-from-2026-03-25-10-59-34.png] 172.30.0.10 is the VM in the same pool as work (172.30.0.30), 172.30.0.20 is the VM from a different pool. I manually set the MTU size in each VM to 1450 just to be sure. I have two pools with one server each. This is due to CPU feature mismatch. Each host is connected via a bond of two SFP+ Ports (which have default MTU 1500) to a switch that allows all VLANs. Using normal VLAN Networks does work with multiple pools.