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)
@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.
@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.
@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.
@jkatz hello, thanks for your report. This topic is being studied on our side, we have scheduled a ticket on it in our roadmap.
We will keep you informed.
Have a good day!