@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.

@rhkean
I used an old laptop for my very first XCP-ng server and ran into similar problems. I plugged a $5 USB network adapter into the laptop and used wired networking. It let me get to the fun parts faster.

If you want to get wifi working, keep us posted!

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)

@acebmxer said in ️ XO 6: dedicated thread for all your feedback!:

yarn run turbo run build --filter @xen-orchestra/web

@acebmxer Thanks for this!
I've been building XO from the source using the documentation at https://docs.xen-orchestra.com/installation#from-the-sources and haven't been able to use XO-6, either. This fixed it.

@olivierlambert
Should we add this to https://docs.xen-orchestra.com/installation#installing-dependencies ? Or will it not be necessary after the next release?

@dani
You mentioned in another thread that you're from Spain.

¿Me ayudas con la traducción al castellano para XCP-ng y XOA?

Apúntate a https://translate.vates.tech/projects/xen-orchestra/xen-orchestra-6/es/

@acebmxer said in ️ XO 6: dedicated thread for all your feedback!:

yarn run turbo run build --filter @xen-orchestra/web

@acebmxer Thanks for this!
I've been building XO from the source using the documentation at https://docs.xen-orchestra.com/installation#from-the-sources and haven't been able to use XO-6, either. This fixed it.

@olivierlambert
Should we add this to https://docs.xen-orchestra.com/installation#installing-dependencies ? Or will it not be necessary after the next release?

Would someone who is a native speaker of Spanish please review the translation in Weblate?

@Pilow Sounds fun, let me know if you want someone else to test!

@rhkean
I used an old laptop for my very first XCP-ng server and ran into similar problems. I plugged a $5 USB network adapter into the laptop and used wired networking. It let me get to the fun parts faster.

If you want to get wifi working, keep us posted!

@tuckertt Are both AD domains in the same forest?

@McHenry Can you put the paging file on a separate disk, and then tag that disk not to be backed up?

@Tristis-Oris My setup is similar to yours, and I get similar errors on any existing backup job.

However, if I create a new backup job, then it works without any error.

ping @florent , maybe these data points are useful.

Like @Tristis-Oris , my first tests were done using a clone of my production XO. They failed with "No NBD" errors.

Creating a new backup works.

Testing a continuous replication backup, I get Error: can't connect to any nbd client

Running the same job on my regular XO works fine. Let me know what logs you want to see.

mail (h2)

   Snapshot
   Start: 2025-04-10 18:18
   End: 2025-04-10 18:18
   h3 local storage (130.02 GiB free) - h3
   Start: 2025-04-10 18:18

Start: 2025-04-10 18:18
End: 2025-04-10 18:18
Duration: a few seconds
Error: can't connect to any nbd client
Type: delta