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

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

@olivierlambert, yes, thank you. I will open that ticket.

@AtaxyaNetwork It will/it does

@olivierlambert Thanks!

removed the failed server connection. Restarted xo-server service. Added new host again. Seems fine now. In hind sight, I could have very well recycled a DHCP ip here as well, if that is a known issue...

Sounds a like a bug to me, we can maybe check what's displayed in there and take a look at xe level to see what's the problem Ping @lsouai-vates

Indeed, you are right and it's about to be fixed very soon. Thanks!

Okay so you deployed XOA, the turnkey VM with XO already installed in it. Are you sure you do not have an IP conflict? Make sure XOA IP is different than the host.

I had the same problem, I had to run the XenClean script and do a fresh install of 9.4.1 which resolved the issue. https://github.com/xcp-ng/win-pv-drivers/releases

Hi, This is perfectly normal. Only the master is the contact point for the entire pool. I would advise to go for manual promotion if you consider your host dead. To do it, go on any slave you want to promote (just one) and type xe pool-emergency-transition-to-master. If you use HA, this will be done automatically, but HA can be tricky. The result will be the same, if the master is down, you'll lose the view in XO about what's going on the pool, until you get a master back.

@olivierlambert Interesting, thanks.

I had a similar issue and found that after changing the static IP directly by editing the network config file inside the XOA VM, things worked fine, but I had to double-check routing afterward. I also ran a quick ip stress test with multiple devices to make sure the new config didn’t cause conflicts or drops on the network. Everything stayed stable after that.

And that's the reason why we planned to keep displaying "out of sync objects" in XO 6

@bleader you have it right. I was checking before I started down the path of writing something myself. We are a public entity that operates very similar to an MSP so we have a ton of VLANs. We're migrating from vCenter/ESXi and have always used powerCLI with powershell to perform these functions.