Ping @Team-XO-Backend

@TeddyAstie I hadn't seen anything special was needed in a VM other that a kernel new enough for support which 6.17 has, is there more to the story with adding things to Ubuntu?

@flakpyro you probaby had multiple job/schedule on the same schedule I reworked the code and pushed an update and added a doc with the edge cases : https://github.com/vatesfr/xen-orchestra/pull/9635/changes#diff-ef545af2ad06f2759c1a3787f266108b3b2cbc203bc8071bbd847278f3e6a5f0 (will be on doc xo when merged ) fbeauchamp opened this pull request in vatesfr/xen-orchestra open feat(backups): improve incremental replication #9635

Living on the edge at my home lab [image: 1774549062491-screenshot-2026-03-26-at-19-08-50-scrutiny.png] In my other NAS the oldest one is closing up 11 years

@kagbasi-wgsdac Hi, thanks for the feedback. That's normal. It was a bug, and the fix was merged into the master branch two weeks ago. It's therefore available for XOCE, but for XOA, it will be available from version 6.3 (release in a few days). Having PATCH enpdoint for all objects (VMs/VDIs/Networks/...) is already in our backlogs but need to be planned. (cc @gregoire XO-2232). Please also note that you can update a inherited VDI directly during VM creation if you know the VDI's user device. (For example: {userdevice: "0", name_label: "foo-bar"}) [image: 1774605903853-capture-d-%C3%A9cran-de-2026-03-27-11-00-33.png] This fix is already planned to be part of the 6.4 release (cc @gregoire XO-1909)

We are running Xen Orchestra with commit c3dcb and the auth-oidc (v0.4.2) plugin. The users that login are unique and not yet present as local users. The OICD provider is SURF with SRAM: https://www.surf.nl/en/services/identity-access-management/surf-research-access-management They support the following attributes/scopes: https://servicedesk.surf.nl/wiki/spaces/IAM/pages/74226142/Attributes+in+SRAM There are some IPs that need to be accessable: https://servicedesk.surf.nl/wiki/spaces/IAM/pages/74226067/IP+addresses#IPaddresses-OIDC . Outgoing traffic from the server to port 443 is open and works. We did try several settings for the Username field and scopes. For example the following: [image: 1774600482742-plugin-resized.png] This should create a user R123456789 The logging shows the following: mrt 27 09:29:48 vm-xoa xo-server[2641104]: Expected values to be strictly equal: mrt 27 09:29:48 vm-xoa xo-server[2641104]: + actual - expected mrt 27 09:29:48 vm-xoa xo-server[2641104]: + 'undefined' mrt 27 09:29:48 vm-xoa xo-server[2641104]: - 'string' If we change it to: [image: 1774600514661-plugin-2-resized.png] The following shows up: mrt 27 09:32:21 vm-xoa xo-server[2641104]: Cannot read properties of undefined (reading '0') I hope this helps to understand the problem. Thanks.

I have two PE R630 and one PE R730xd. The two R630s show the IPMI data in XO but the R730xd does not. If I run ipmitool sensor from an ssh session, I get very similar data back on the 730 and 630. This isn't critical to me, just letting you know that there are cases that functioning ipmitool on a Dell does not seem to be enough to show it. There are some differences in the labels. The R730 has "Fan1 RPM", "Fan2 RPM" while the R630 has "Fan1A", "Fan2A", "Fan1B". Most of the other interesting fields seem to have the same names but the order is a bit different and I didn't do an exhaustive comparison. It's very cool that you are surfacing this data now.

And this is the result [image: 1774531386302-screenshot-2026-03-21-at-09-31-45-backup.png]

Ping @florent