I've set up a test-environment and indeed it worked. Commvault was (is?) checking for specific version/agent string when connecting to XS/CHV/XCP-ng and in older versions refused to connect to XCP-ng. I successfully installed the agent on a proxy-vm (it uses a proxy to ro-mount the VM-VHDs and backup the content), connected the pool, delivered the VM-inventory and also ran a successful backup: [image: 1666711412304-171c0956-e3e2-4fb9-a93b-48a2be6751bb-grafik.png] In other words: If you're using Commvault (11.28+) you're not any longer locked on Citrix.

This section has nothing to do with XOA IP address, but useful to restrict some VMs to some IP address. I agree it's unclear. But as I said, for now, there's 0 GUI to configure the system per se. That's why I said it could be an addition sure, but there's nothing yet, so adding it will take some time or efforts, and it's not a priority as we speak (our backlog is already pretty big). But again, as an Open Source project, we are welcoming contributions!

It's hard to tell. Let's say next time it happens please report

@olivierlambert Then keep it in mind for that.

Yes, that's the issue, the max vCPU in Advanced tab. It's probably at 42 while you only have 32 physical CPUs. Therefore, the VM won't boot. See an example screenshot: [image: 1726217639918-8728f260-893b-4601-b8b2-43b39b9d6806-image.png]

No it's not how it works in XAPI. You need a dedicated ISO SR using only *.iso file name/extension.

Thanks for feedback, it's corrected on the blogpost