@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

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

I'm still getting "Cannot find module '@vates/generator-toolbox'" errors when I try to build it. I'm using the 'feat_generator_backups" branch.

I found this while investigating repeated backup failure reports. The error report says "NO_HOSTS_AVAILABLE()".

I finally noticed that the user had removed all of the disks from the VM.

Could the backup code be adjusted to ignore VMs that don't have disks, or to return a different error?

@RawbDeeni
Can your XCP host ping xoa.io?

@kagbasi-ngc
First, a disclaimer. It's been a while since I last designed an HA solution for AD. Things may have improved.

You should reconsider your approach to designing a highly availability AD. Configuring the client to guess which AD server to use will work fine, but only as long as both AD servers are healthy. If there is ever a problem between them, you will have no control over which AD the servers hit.

If I remember correctly, best practice for highly available Active Directory is either to use Microsoft's AD VIP solution, or to use round-robin DNS (multiple records with the same name but different IP addresses). Either way, all of the clients in a single domain should have the same configuration.

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

@julien-f said in Enhancement suggestion: Filter showing VMs that don't have the agent installed:

XO does not support this for halted VMs but that could be added indeed.

Can you change the title of my thread to "Enhancement suggestion: Update 'ManagementAgentDetected?' to support halted VMs" ?

A filter that only lists VMs that need the agent installed would be very helpful. Here are a few thoughts.

1. The "has agent" mark should persist after VM shutdown. Can we use tags, or should we look for an alternative?

2. VMs that have the agent running should be marked as having the agent. Can we update the agent so that it add the tag itself at startup?

3. XO should remove the marker from any VMs that have been running for more than 5 minutes and do not have the agent running.

With this setup, it is easy to determine which VMs need the agent, including VMs that are shut down at the moment.