No luck, I've tried building from source, using the script, etc. Following along with Google Gemini I even managed to get walked into the process of damaging the Xapi to the point of losing access to the server from Xen Orchestra / XCP-ng Center (unfortunately for me it was the Pool Master). Thankfully I had backups on my NAS and experienced minimal loses through the process of having to reinstall the operating system. At this point, I'm guessing my pool that dates back to version 8.1 is screwed up in some way beyond human or AI understanding. I have 2 Servers & 3 NAS units (2 TrueNas Scale) + 1 Synology that all work with the old version of Xen Orchestra but I can't get it to work with anything else. Manually putting the same info in or importing the configuration. One of the servers was rebuilt today and added back to the pool. Is it possible that reinstalling the OS on the other server could fix everything? I'm confused because the backups aren't failing from the old Xen Orchestra. Old: [image: 1756784257357-19e6f3da-3b22-4f7d-a47e-66d8216b3f8b-image.png] New: [image: 1756784292273-263493de-a5cb-4610-b7ba-ba173fe7b055-image.png] Any help and / or ideas would be greatly appreciated. Thanks!

looks good Xen Orchestra, commit 384bb Master, commit 384bb thanks for quick fix

@AlbertK said in XCP-ng - XOA vs. XOCE: @Danp , Is it possible to add the comparison of the XOCE together wit XO in this page?. https://vates.tech/pricing-and-support/#features-matrix XOCE is a term that I came up with when I originally started writing the deployment script that exists today. It's stuck around. Vates uses the terms XOA and "XO from Sources" as their unique products. XOCE would be "you used a github script to deploy" (my github) XO. XO from Sources is a completely manual process where you're following the documentation to deploy XO. This approach gets you the same thing that XOCE does, but takes longer to complete since you're finishing each step over SSH rather than running a single bash command on a Ubuntu/Debian VM.

That's why XO proxies are great and the go-to solution Alternatively, you can deploy an XO inside the target network and manage your hosts from there (but you won't have the unique central console with one XO+proxies for the entire infrastructure)

@acebmxer Hello, the XO team is currently working on a solution. We will keep you inform as soon as it is on release.

I will create a new thread from your message

@AtaxyaNetwork It is Debian 12. I found the problem and will post again if there's more issue. The VM stopped using its static IP, not sure how that happened, but I re-added it to /etc/network/interfaces and it's working again.

Hi @Andrew. This PR should fix your issue https://github.com/vatesfr/xen-orchestra/pull/8854 MathieuRA opened this pull request in vatesfr/xen-orchestra closed fix(xo-server): fix incorrect state when remove server #8854

@DustinB That pic was taken from the host tab. But yes I removed from the settings tab and host 2 still shows under pool 1 and all looks ok. Thank you.

@pierrebrunet fixed now, thanks.

@Danp THANKS! That did the trick. I was able to clean up after doing that. Thanks so much!

@olivierlambert Yes sir, it is and I'm glad I confirmed this for myself. Thanks also for helping me understand how the VM Suspend process works. Hopefully this post helps other newbies with the same understanding in the future.

@Razor_648 While I was writing my previous message, I have been reminded that there are also issues with LVHDoISCSI SR and CBT, you should disable CBT on your backup job and on all VDI on the SR. It might help with the issue.

@dinhngtu Thank you so much. If you want me I'll be at the pub.

Hey @Danp , I can keep my cluster without this node up to Monday, do you have an idea / do you want to investigate on this case ?

@gb.123 Interesting -- alert the XCP-ng team to take a closer look, if they haven't seen this already.

@andriy.sultanov After running that command I didn't have anything returned.

@ph7 worked, ty.

@lsouai-vates Duly noted. If amd when you do get a moment, could you have a look at https://xcp-ng.org/forum/post/94297 and offer up any guidance on how I can stop the debug log entries and also the double timestamp entries in the audit.log file? Thank you.

@kagbasi-ngc You are welcome.