@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

@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.

@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.

@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

@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

@acebmxer good news! XO Team is totally aware of these "loading in progress" issues, and it will be fixed in the next release which will be released very soon.

Don't hesitate to inform us if you see another UI issues.

Have a good day!

@acebmxer hello! thanks for your feedback on Xen Orchestra 6, I'm asking our XO Team and wil come back to you when I have some answers.

@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!

@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

@StephenAOINS Hello, I'm asking XO team about it.

@icompit @Bastien-Nollet can you help to answer?

@olivierlambert I agree, ping @thomas-dkmt

@icompit hello again and sorry for the late answer...

The current backup logging system is being reworked: instead of using a custom task system and compiling logs on the fly, it will soon rely on the generic task system and store precompiled logs.

As part of this change, the logic that currently causes a backup job to appear as "failed" — even when a retry succeeded — will be deprecated. So while fixing this specific issue now would be technically easy, it might introduce regressions and won’t be relevant once the new system is in place.

In short: this will be naturally fixed by the upcoming logging overhaul. Thanks for your patience!

@olivierlambert can you close this thread?

@ph7 happy to read that