that log appear again, without any actions from my side. [image: 1713513115366-bab449b6-55cb-4e9f-b0af-ce8e9bb19d22-%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5.png]

@CJ It may be easier to ensure reliability and prevent other possible issues from happening. I'm not an expert when it comes to the underlying code, but I would take an orphaned VDI over say some form of corruption or something like that. I'm guessing a little if I'm being honest, but cancelling it mid transfer might break some things, could leave a partial VDI that is locked for example, etc...

@gb-123 AFAIK the host doesn't call XO, if you shut XO off, the private network would continue to work but its state wouldn't change. It means if you restart an host etc the connection to this host would be lost. The logs depends on how your installed XO or XOA etc so you might want to go through our doc! Cheers

@ptunstall Great!

Hi, Because it's not implemented I'm not even sure if we have this info in the XCP-ng's API already (I mean VDI stats), probably worth checking.

@bdacasc said in Raid: @Danp I am running 8.2.1. The only thing I want to know if something happens to may softraid. Looking in the advance tab I only have "system disk health" and that is empty. It's not available on XCP-ng 8.2.1, it's only available in the beta 8.3, and eventually in the future release. That is why the "system disk health" is empty.

@palova XO can be installed and used from anywhere, you could even have multiple XO instances running simultaneously on different systems all with access to the same singular host, just avoid having those instances run backup jobs etc. It would be much easier to have XO running somewhere so you could administer this host before and post migration - that isn't running on either system. Make sure you export a copy of the running configuration from XO you have now so you can import it into the final XO system once all migration work is completed.

The task always has a progress, but I agree it's weird. We could update the UI to make it more logical in our next new UI

@gskger No problem, I just didn't understand the relationship with truenas' tls. I'll wait to see if anyone else goes through this and in the meantime I'll continue my studies with nbd. Thanks

@olivierlambert I have not. I looked at it last year but haven't checked on it since. I just tried it now and I remember one of the reasons I haven't used it. The self signed certs give my browser fits and I have to open each host up in a new tab to accept them by IP. The console UI seems to work the same in XO lite as in XO. There doesn't seem to be any way to copy and paste.

Nope, that doesn't exist at the moment. But I'm not certain how that would work exactly, at least I've not thought about it here.

@Danp said in xo-cli not found on XOA: @DustinB A newer version based on Debian 12 was rolled out within the last month or so. You would need to deploy a new instance of XOA if you wanted to try it out. Redeploying now. .

@julien-f Wanted to check on this as the fix didn't correct the issue. Thanks Mike

@gskger huh, well then this is particularly odd because the VM came from the same destination! Literally it was migrate A->B (which went fine). Immediately try to migrate B->A with the no host available error. Host B here is the non-VT machine. Not to mention these were stopped VMs. They aren’t taking any resources - just disk.

Okay, good to know

Thank you! Obviously, this wouldn't be possible without our great community

Expect some visible news for our April's release!

@Danp Thank you very much!

@bleader Thx for your answer and good to know

@julien-f Tested. Fixed. Thx!