@AlexanderK Yes. The hosts and CS Management server are on the same L2/no firewalls. I think it has to do with me wanting to use an "L2 network topology" out the gate but from the reading I'm doing, this is definitely atypical. I've blown away the zone and reconstructed it in what I think is a "normal" CS config now.
I've gotten the hosts attached at least, but now I'm seeing issues with getting the SystemVMs up and running. I did check the 'use local host storage' option in the zone config and I can see CS is at least touching/renamed the local SR.
Secondary Storage Vm creation failure in zone [xxxxxx]. Error details: Unable to allocate capacity on zone [2] due to [null].
Console proxy creation failure. Zone [xxxxxx]. Error details: Unable to orchestrate start VM instance {"id":20,"instanceName":"v-20-VM","type":"ConsoleProxy","uuid":"f138df9e-92c4-4cfd-9333-7d8396c436e6"} due to [Unable to acquire lock on VMTemplateStoragePool: 31].
My storage network is completely private and everything is hanging off a single bond0 where I have VLANs carved down to the XCP-ng host, but I haven't configured any networks within XO. I assume CS was supposed to take care of that?
I'm also not seeing the VMs show up in XO. Am I supposed to see instances and SystemVMs in XO?
Thanks for any help.
