I haven't really done HA setups with XCP-ng before, so can't really speak to how good it is. But IMO CR and other backup jobs like that are more meant for geo replication and stuff like that (i.e. a disaster recovery scenario with some offsite XCP-ng host). Which is why I'm asking about location, personally don't see the benefit to CR if in the same physical location, I'd be more interested in HA at that point.
@kevdog You can force a host to be ejected even if the host is not reachable any longer from the pool master using:
xe host-forget uuid=UUID
If there is any issue because VMs are thought to be running still on that host,
you may need to do a power state reset on such before you can get rid of that host.
See if that works for you.
@mauzilla In the past, I have run into this problem when introducing a new host into a pool and the primary management interface was picked up on the non-primary bond. To properly add a new host to a pool, only the primary management interface should be configured on the host and correspond to the subnet of the primary on the pool master. Just mentioning this because I ran into it before, even if it turns out not t pertain to your specific case.
Also, I have run into a host before - the exact same hardware as another - where one Ethernet NIC showed up in a different order than on the other server -- even though it was on the same card! I had to use the interface-rename application to switch it around and make it match.
Strange things happen.
Just an FYI, I have not tested the latest Scale 22.12 RC1 for performance but the previous versions of scale under some conditions was quite a bit slower. I have a video covering this topic here with the benchmarks and methodology used for testing.
@mauzilla To boot an ISO in a VM, you need to select "DVD" in the boot order, put it first, and hit "Save". Then boot the VM.
For ANY system (real or VM), you need boot it with the same type of bootstrap as it was installed to use. BIOS or UEFI. If you change the boot type then you have to make the OS ready to use the new/different settings (not just a VM problem).
If you created a Windows image from a working system that booted with UEFI then you have to copy ALL partitions (the whole disk), not just the C windows drive.