@olivierlambert so strange though. i have it enabled on 4 pools, that didn't propagte on hosts. still VM boots up when not needed as explained on fist post of the thread. i'll try différent combinations to see what's really going on

Thanks, we need to update this!

@gb.123 what xen and gurst version etc were you using? I'm about to try GPU PT and having USB st the same time is important

Hello All, This issue seem to completely go away on a older branch/tag if i build it from below for XO: xo-lite-v0.17.0 So the issue I would think is coming from the newer version of XO. Not sure best way to test this. So I am going back to an older commit. If anyone has any suggestion I can try helping as its an annoying issue.

@jkatz So everyone is cleared since I just experience the same issue not allowing me to create a new vm using the template. Before you use the Windows 11 Template and you have it with SYSPREP ready. You need to go down to advanced and make sure you delete the VTPM [image: 1769552292859-5d61aad5-013e-4cff-af7c-adbb4c4ca809-image.png] then create the Template. Once you create the vm again you will not receive the error and a vtpm will be created for the new VM with no issue. Hope this helps.

You can forget them, no issue.

@pdonias https://docs.xen-orchestra.com/users [...] Operator An operator can make everyday operations on assigned objects. For example, on a VM: eject a CD insert a CD (if he can view the ISO storage repository) start, restart, shutdown, suspend/resume it All other operations are forbidden. [...] As I understand it (I may be mistaken), changing the "Rate Limit" is already a configuration change and should not be available to an Operator.

Indeed, it's hosted in Lyon, so an issue could happen in many places in the middle ^^

I don't think stop will remove it, probably better to yum remove it. For Openmetrics, check: https://docs.xen-orchestra.com/advanced#openmetrics--prometheus-integration I switched our own production to that, so far it looks promising.

@Pilow the rrd ( the stats ) use the same code path as the backup . I am not sure if it's a feature or a bug, but at least it's a good canary the data volume of stats can be quite huge and have an impact on management. So it's a little justifiable to use the same network for backup and stats, at least until we can separate things more clealy . At least it helps a lot to check if the network is really reachable (sometimes because of third party filtering or ip configuration error , other to the xoa missing some network), and the downside is not to dangerous.

@bvitnik Thanks for giving more details. I will give a try with each of them (netplan, ..etc)

@acebmxer It's not pretty, but its failsafe. The proceedure looked like this in our case: Disable HA in the "old pool" Put a host in the "old pool" into maintenance mode Reinstall that host and connect it to XOA and then patch it Create a "new pool" from that host Create a new LUN or NFS share in the SAN for "new pool" and attach it to "new pool" Live migrate VM's over from "old pool" to "new pool" Once you've freed up another host you repeate step 2 and 3 and then join that host to "new pool". It is important that you patch it before joining it to the pool, that is done by going to Settings -> Servers in XOA and connect to it manually. And then just continue untill you're done. Live migration is pretty reliable now days, so this works pretty good and since we had 10G network its not taking as long as it used to do with 1G network. We did this after a major incident on our primary production site where 2 out of 4 hosts in a pool "suddenly" lost their NIC's after updating them. Since then we never updated the pools again. Standalone hosts are fine tho, they never did this. Luckily we had 2 other pools where we could migrate the VM's to, but we couldn't realy trust the updating after that.

@olivierlambert thank for that. Just to be clear the vm was not runing but shut down if that makes a difference. @ph7 Both firewalls are Unifi Enterprise fortress gateways. - https://techspecs.ui.com/unifi/cloud-gateways/efg?subcategory=all-cloud-gateways Both sites are setup with Site Magic VPN. So should be full 1.1gbps if accurate. [image: 1767705099263-screenshot-2026-01-06-081123.png]

Cool, thnx for the info!

And my cloud config: #cloud-config hostname: {name}% Network config: network: version: 1 config: - type: physical name: enX0 subnets: - type: static address: 172.1.1.2 netmask: 255.255.255.0 gateway: 172.1.1.1

@pierrebrunet thanks for quick insight/fix, got back to stable to deploy templates, it is working

@itservices Thanks Marc

Not until we can have our own piece of code doing it. Right now, it's a binary that's not Open Source made by Citrix, we cannot legally re-distribute it.