@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

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

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

@Kptainflintt you are welcome We are always delighted when we can quickly unblock a user!
Have a good day and don't hesitate to come back if you have other issues in the future.

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

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

@ph7 @coolsport00 thanks for the report, this topic will be adressed in our roadmap 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!

@bryonadams said in Trouble Creating VM via API:

Is there a place I can submit a feature request to allow setting a description and other settings from the UI to get feature parity when creating a VM? Otherwise, there's not much point since I have to go in and touch the new VM anyway. Unless I'm going about this wrong to begin with?

You can create a feature request on Xen Orchestra github repository (https://github.com/vatesfr/xen-orchestra/issues), and if you have subscribed to support via XOA you can send a request through Zammad.

@bryonadams as you are on XOA, you should switch on latest to get the last udpates yes
Hope it will help!

@bryonadams Can you precise if you are using XO from source or from XOA?

The update action you are dispalying is for XOA, and our XOA is now on 5.109.1...

If you are using it from source, please follow https://docs.xen-orchestra.com/installation#updating

Keys or values from a GET should be usable in a POST.

@bryonadams I understand your point of view and the reasoning behind it. However, it’s not always an absolute rule that every field returned by a GET endpoint can be passed back to a POST (or PUT).

In this case, the API error message you received clearly indicates that these parameters are “excess properties not allowed”, meaning they cannot be used as input parameters.

Indeed, it also seems you’re not running the latest version of XO. Could you please check again? You should be getting the recent REST API updates:
https://github.com/vatesfr/xen-orchestra/pull/8798

We’re currently in the process of migrating from the old REST API to the new one, so for now Swagger remains the single source of truth. As @olivierlambert mentioned, we plan to provide direct access to it from XO-6, and we’ve been communicating about this in our blog posts.

MathieuRA opened this pull request in vatesfr/xen-orchestra

closed feat(@vates/types): enhance createVm type #8798