@CodeMercenary hello and thanks for this idea! We will discuss about it with @clemencebx and see what we can propose on new XO-6 design and workflow.

@hanzzz Hello, indeed I agree that we need to add this to the hosts actions to handle by REST API.
Let's add this to our futures features on the REST-API

FYI @MathieuRA

@Pilow @olivierlambert the "stacked" tags are already in our Design System :

Just a little patience, it will happen in 2026

@flakpyro yes, indeed that exactly what I was talking about. The XO6 new interface will provide more information, but I am noting the missing type of bound to discuss it with XO team for next feature.

@ph7 Hello, XO-6 does not yet support reactivity in data retrieved by the API, so you have to reload the page to get the updated information. This is in the pipeline and will arrive very soon.

@acebmxer Hello,

We’re aware of the Backblaze rate limits and this isn’t the first time it’s been raised. We’ll be looking into this on the XO side, studying different options such as caching restore points to reduce API calls. Longer-term improvements, possibly tied to advanced XO6 dashboards, are more of a 2026 horizon.

Thanks for bringing this up!

@McHenry hello, thanks for the report.
Can you open a suggestion on Github so we can plan it or next roadmap?
Have a good day.

@olivierlambert transfered

Hello @manilx and thanks for your reply.
I am asking the XO Team and will keep you in touch.

@JoaoL Hello and thanks for the information. I'll inform the XO team.

@acebmxer Hello, the XO team is currently working on a solution. We will keep you inform as soon as it is on release.

@Tomcatter yes it was already implemented in XO-Lite

You can find it from the pool view. (click on a pool on the treeview and then on the VM tab)

It is also planned for XO-6, it is in our backlog for next features.

Does it respond to your questions?

@Tomcatter Hello!
In the rest-api doc you have this endpoint: https://github.com/vatesfr/xen-orchestra/blob/master/packages/xo-server/docs/rest-api.md#vm-export
Maybe start with this and create a script to convert result to CSV/Excel?

Does it help you?

@olivierlambert it is planned
@IvanK We're gradually migrating endpoints to the REST API and will create new ones later.
I know it can be frustrating not having everything ready to use, and we understand that... We do our best

@Kptainflintt Hey! XO team dev is doing a fix on it: https://github.com/vatesfr/xen-orchestra/pull/8979

FYI @pdonias

pdonias opened this pull request in vatesfr/xen-orchestra

closed fix(xo-server/resource-sets): only edit limits if `limits` is passed #8979

@olivierlambert I am asking XO Team about this issue.

@StephenAOINS
This endpoint is not currently present in our REST API swagger, but we do plan to add it to the list of endpoints.
We are currently finalizing the migration of existing endpoints, the next step will be adding new ones.
We will keep you informed when it is available. Feel free to come back to us if you want to learn more and follow our blog posts.

have a good day

@Pilow I know, it is like waiting for the part 2 of your favorite movie saga...

As @olivierlambert said, we will do our best to release this in early 2026, but we have plenty of interesting topics to come on XO-6

@bjdemon Hello, and thanks for you report! We are aware of this issue, and we already added it to our roadmap

We will keep you inform when it is ready!

Have a good day!

@ScarfAntennae hello, and thanks for the suggestion.
I am discussing it with the XO Team to add it to our next features.

Have a good day!