If I read the docs right, most of what you're describing exists now, under the name RBAC (it was called ACL v2 while it was being built). There are eight built-in template roles, including Read only, VMs creator, Network administrator and Storage administrator, which map pretty closely onto your list: https://docs.xen-orchestra.com/users-and-access/rbac#built-in-template-roles. The groups and ACLs @acebmxer mentioned are the older XO 5 system. As you found, the same page says role management currently goes through the REST API, so it's the Swagger page and not buttons in XO 6. Since you're on XO from sources there's no restriction, but for anyone reading this on XOA, the same page says RBAC comes with the Essential+, Pro and Enterprise plans. A UI for that sounds like a good one for https://feedback.vates.tech/, I don't know whether it's already planned.

@coolsport00 Yes I can see the appeal, but for a server sitting in the corner of the living room that basically only hosts a NAS, torrent seedbox and an all around appliances management platform, two hosts sounds like a complete overkill and a headache, haha.

For the partitioning part, the docs say NVIDIA vGPU isn't supported on XCP-ng, since it depends on a proprietary XenServer component that can't be redistributed: https://docs.xcp-ng.org/compute#vgpu. So as far as I can tell, the "20, 40 or 80 GB per VM" split won't work through vGPU. Passing a whole GPU to one VM is the documented path, on the same page. I haven't seen anyone report on H100 or H200 cards here, though, so I can't tell you if that class of card brings its own surprises. There's also a blog post doing LLM inference that way on a much smaller Tesla T4: https://xcp-ng.org/blog/2025/07/28/your-own-gpu-powered-llms-with-xcp-ng/. There's an open design discussion upstream in XAPI about GPU partitioning, MIG included (https://github.com/xapi-project/xen-api/pull/7260), but that's the XenServer side, and I don't know if or when it would reach XCP-ng. As GPU partitioning matters for your project, it might be worth opening a request on https://feedback.vates.tech/ with what you described here (H200s, LLM inference, several tenants per card, fixed VRAM per VM). From what I've seen, a concrete use case like yours carries more weight there than a plain "please support vGPU", and other people needing the same thing can vote on it.

My guess, and I'm not an AD person so take it lightly: sAMAccountName holds the short login (jdoe), while userPrincipalName is the jdoe@yourdomain form. So if you typed the full address in the Test box, the first filter would find nobody. Was that the case? The docs list both filters but don't really say when to pick which: https://docs.xen-orchestra.com/users-and-access/users#ldap. On the logging, if I read the plugin code right, it already logs how many entries the filter matched at debug level, it's just that the Test button only gives back "could not authenticate user". Showing that in the UI sounds like a good one for https://feedback.vates.tech/, where the XO team tracks this kind of request.

@nathanael-h I know you're suuuper early in your process. But would it be possible to have podman be an alternative to Docker too?

Hello all, Version 9.2.445 of the XCP-ng Windows Guest Tools has been released. Download the latest release here: https://github.com/xcp-ng/win-pv-drivers/releases This release brings important bug fixes to the Windows drivers and installer. Important note for users upgrading from 9.2.350: You must first install the XenTools-fix-9.2.351.msp hotfix to upgrade to 9.2.351 before installing 9.2.445. Otherwise, upgrades from 9.2.350 will be blocked. Reboot is not required after installing the hotfix. The installer downloads include a copy of XenClean and XenBootFix. It is not necessary to run XenClean when upgrading from previous versions of the XCP-ng Windows guest tools, unless prompted by the installer. Remember to carefully read XenClean docs before use. Note: Always download the latest XenClean/XenBootFix from https://github.com/xcp-ng/win-pv-drivers/releases . You can find them in the latest release ZIP/ISO archives. Before installing Thank you for using our Windows PV tools. Please carefully read the instructions below. It is not necessary to run XenClean when upgrading from previous versions of the XCP-ng Windows guest tools, unless prompted by the installer. Not compatible with the "Manage Citrix PV drivers via Windows Update" option. You must disable this option before installing. Changes since 9.2.385 NEW: Group Policy support (see the extras/admx directory in the source code tree). Supported policies include: Hide the tray icon Disable all features that allow controlling the VM from the host Improved: Better network performance. Improved: System reliability improvements on driver upgrade failure. On an upgrade failure, the installer will remove all Xen drivers to ensure that the system will keep operating, and to allow you to safely uninstall the existing driver package. Improved: Remove obsolete Windows Update devices and don't block installation because of them. Fixed: Fix further data corruption bugs during memory snapshots and backups. This driver version significantly narrows the corruption window. However, fully fixing all known corruption issues requires further work in other XCP-ng components. Please keep an eye on the XCP-ng blog for updates. Fixed: Fix loss of VBD connection after storage migration. Fixed: Improve reliability of the clipboard service. Fixed: Improve reliability of the VIF IP configuration feature. Fixed: Reliability fixes on VMs with many vCPUs (>64). Fixed: Many other driver reliability fixes. Help / Community support If you encounter installation/uninstallation errors, please try again with one of the following commands: For installing: msiexec.exe /i XenTools-x64.msi /l*vx install.log For uninstalling: msiexec.exe /x XenTools-x64.msi /l*vx uninstall.log Please include this log along with the file C:\Windows\INF\setupapi.dev.log in your bug report. These files will help us troubleshoot any installation issues. Additionally, please report any errors or BSOD you encounter during testing of this release. Your feedback is very appreciated.

@poddingue Yes, reads pretty much like the same error / root cause.

@poddingue Taking the time to do this it's the bare minium! Here you go: https://github.com/vatesfr/xen-orchestra/issues/10741