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!

We could use scoped tags to structure at least one level of folders easily without changing anything in the backend

@Aeoran AFAIK, the XAPI database gets wiped whenever you add or remove the host from a pool. You may be able to restore metadata to the old master once it is no longer belongs to the pool, but I can't guarantee that this will work or not produce other issues. If you don't have backups of the VMs, then you should be able to copy the VHD files to another location by accessing the directory /run/sr-mount/<SR UUID>/ on the old master.

@olivierlambert - it has been resolved.

Solved by 583c728

Ping @julien-f in case it was missed

@paulorrockgit This is clever!

@Danp Thanks for the tip bud! I will search that topic and experiment some more.

Its almost certainly goes through XOA. When I was moving from Esxi to XCP-NG I abandoned the process, then beefed up my XOA memory and CPU cores and it sped up marginally. That was a while ago, some of the VM's I had to use Clonezilla on (too large and kept failing). From what Ive read the migration tool has improved dramatically since then.

If you have hardware that supports this you can try to do an openvpn Server as a TAP adapter. it will be closer to a Layer 2 MPLS connection than an IPSEC tunnel. I have no idea if XCP-NG or XO/XOA use any type of Multicast traffic to communicate. Thats the only thing I can think of unless you have IPSEC firewall policies blocking some type of traffic that XO needs. I presume you can ping/ssh into the remote host? Are these hosts using shared storage over the MPLS/IPSEC? Edit: I just found this as well. https://xcp-ng.org/forum/topic/6609/unable-to-join-a-host-to-a-pool Seems to be also that the XCP-NG hosts will attempt to talk to each other over local URL's in some cases but I can't find a post about that. Bridging the two networks the same way the MPLS was would likely get you back to the way it was.

I found the problem. I am using OPNsense and forgot to disable TX checksum offloading. Very interesting that this checksum offloading caused catastrophic network disruptions on a Realtek nic, but no noticeable performance hit on Intel nics. This was an old host that featured a Realtek card. All my recent hosts that I use have only Intel nics. That is why I forgot about the whole offloading thing. Thanks for the tips. Best wishes to the whole community!