@Andrew All virtualisation options are enabled. It is an HPE DL360 Gen11, my first of that gen. Never had setup issues with Gen10. I'm focussing on the Intel network card - the NICs are not visible to XCP-ng. I have installed the Intel hardware driver for Redhat, installed with no issues. That made no difference.
Has this issue happened before?

XCP-ng 8.2 and 8.3 both do not see the Network ports (Intel adapter 1350T4 ocpv3)
I am able to update the adapter firmware through XCP, so the hardware is visible. Intel has Linux drivers for this card, for SLES and Redhat - which is more suitable for XCP?

@Andrew all that was okay. The proxy string was incorrect, now working. Thanks

A new pool has been added with new servers, all functioning in XCP-ng Center. The pool master has been added to XOA, but does not show in the list of hosts, and the pool is not added to list of pools. Any advice please!

Running XOA Enterprise, have just added a fourth host pool. Only 3 pools can be seen at any time: if I restart XOA appliance, it will still be 3, but not necessarily the same ones.
XCP-ng sees all the pools - is there a limit on XOA Enterprise?

@akurzawa thanks, I have been doing that. I was looking for a lazy way to move 20+ VMs out of a partition.

Good to know that's on the way. Yes, have been using VM view

I hope there is a way to migrate all virtual disks from a partition. There is 3TB of data to move, it would be great to queue it up and let it run.

I think this is what happens when you ask XOA to move a disk into a different resource pool, and that pool can't see the storage. Discovered that by accident

Olivier - the destination storage was attached to the wrong pool. It was behaving correctly, but not doing what I wanted.

I am moving some VMs to different storage, into a large NFS partition. My hosts are grouped into 2 pools, which have different purposes, so I run different VMs in each pool.
I am copying the VM, then deleting the original, as there is a problem with the existing storage. Every copy I make from pool1 is ending up in pool2. That is surprising since I never added the destination storage to pool2, but XOA can see it all and just makes it happen.
Is there a way I can make XOA copy into the original pool?

@borzel I am moving some VMs out of a storage pool, by moving the disks. For each VM in that storage, I get the error above.
The VMs are healthy, and I am able to copy them instead, then remove the original copy.
Pretty sure the problem is on the storage side, which is why I am migrating out of there.

@2planks The same is happening for other VMs on the same storage. Using ISCSI

In XOA, migrating hard disks for a VM, it immediately fails with the above error. The VM starts and stops, disks visible in XCP-ng and XOA.

It looks like I can remove the remotes and set them up again, and configure the backup jobs to address the new share. That's okay, there are not too many.

XO it is! When trying to connect, it returns messages like "no such remote deba2cbe-a610-47d8-99f2-14d49d08ab95"
The mount points are there under /run/xo-server/mounts.
Eventually NFS times out. I can connect to the same shares from XCP-ng as remote storage, so the NFS sharing is fine.

Running the same mount command from command line in XO also times out

Using XOA from the sources, upgraded with git. It looks okay except the remotes are not mounted - should there be entries in /etc/fstab? It is empty apart from / and swap