@ph7 that's fine, keep on testing our new XO-6, we are very happy with all our community feedback

@edsilber After exploring the UI, I confirmed that it's not possible to schedule a one-time cron job from the XO-5 interface.

We're prioritizing the development of new features for XO-6, so we'll take your suggestions regarding scheduling into account for the new interface.

I propose an alternative: using the REST API to run schedules by creating your own execution script (if you are on linux: https://www.veeble.com/kb/scheduling-one-time-jobs-in-linux-using-at-command/).

The REST API link is: {your-xo-url}/rest/v0/docs/#/schedules

Please feel free to contact me if you have any further questions.

@edsilber Hello and thank you for your help! I'm currently reviewing the user interface and discussing it with the XO team. I'll get back to you as soon as I've found the best way to help you…

@ph7 XO-Lite and XO-6 are 2 differents projects, so no they are not using the same code, even if the UI looks similar... ^^"

@ph7 hello and thanks for your reply.

The current XO-6 form is not yet finalized... we are still working on it. An informational message will be added to indicate what will and will not be possible to manage in this version of the form. The final version is planned for early 2026, and we are working as quickly as possible to provide all users with the best possible experience on this VM creation form.

We apologize for any inconvenience and will do our best to minimize it.

@kagbasi-ngc hello! For now the token has to be added in cookie, why do you need to send it by url?

@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

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

Just a little patience, it will happen in 2026

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

@vmpr hello, to be able to address the problem more clearly can you give me the version of your XO please? and if you are on stable or latest? XO v5.111.0 has been publicly released in latest channel yesterday.

@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