@florent I'm doing this from source.
Running git pull --rebase seems to have fixed the build problems.

@yzgulec
You might build your first pool using your existing rules (eg, pCPU:vCPU = 1:3). As business expands, you will gain experience that allows you to adjust your rules when building future pools. I would be interested in hearing what you find.

Be sure to give the control domain (aka "dom0") enough RAM.

The hosts in a pool should all be the same - same CPU type, same number of cores, same amount of RAM, same number of network ports, and a consistent network design.

@kassebasse said in Remove running host:

I am just trying to remove the host, because it is no longer exists

In that case, try

xe host-declare-dead

You will need the prior UUID of the host, that is, the UUID assigned to the host before you reinstalled xcp-ng.
xe host-list will provide that.

Read the warnings about host-declare-dead carefully.

The existing technical documentation is great. An operations guide would be helpful. Here are a couple of chapter ideas:

1. Best practices for setting up your environment
   (eg, odd number of hosts, isolate management network, treat your hosts like cattle, etc)

2. Preparing for disasters (eg, requirements for restoring pool metadata, how to recover a single VM if your pool data is gone, etc)