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

Posts
-
RE: Display Dashboard in NOC Using Authentication Token
-
RE: [Request] Improve XO6 tags display functionality
@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
-
RE: [Request] Improve XO6 tags display functionality
@Pilow @olivierlambert the "stacked" tags are already in our Design System :
Just a little patience, it will happen in 2026
-
RE: XO6 dashboard and backup view feedback
@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.
-
RE: ldap user auth doesn't work after update to actual version
@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.
-
RE: Why changing objects in resource set wipe limits ???
@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. -
RE: Why changing objects in resource set wipe limits ???
@Kptainflintt Hey! XO team dev is doing a fix on it: https://github.com/vatesfr/xen-orchestra/pull/8979
FYI @pdonias
-
RE: Why changing objects in resource set wipe limits ???
@olivierlambert I am asking XO Team about this issue.
-
RE: Cool way to indicate retention reasons on backups
@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.
-
RE: Boot New VM to ISO in XO-Lite?
@ph7 @coolsport00 thanks for the report, this topic will be adressed in our roadmap very soon.
-
RE: Restore list & S3 Backblaze
@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!
-
RE: Trouble Creating VM via API
@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.
-
RE: Trouble Creating VM via API
@bryonadams as you are on XOA, you should switch on latest to get the last udpates yes
Hope it will help! -
RE: Trouble Creating VM via API
@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
-
RE: Trouble Creating VM via API
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/8798We’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.
-
RE: Trouble Creating VM via API
@bryonadams, have you checked the API Swagger?
{your URL xo}/docs/#/vms/CreateVm
As I said before, the three values you entered cannot be sent during VM creation. That's why you received this error message.
But I agree, this message is not very readable and we should improve it.We will investigate how to improve their readability in our future roadmap.
-
RE: Trouble Creating VM via API
@bryonadams it seems like you are not on the most recent version of Xen Orchestra. Could you update your XO?
"excess property" errors are often wrong parameter errors.
name_description and memory are accepted but the auto_poweron parameter is not allowed because it is misspelled... the API expects autoPoweron.
-
RE: Trouble Creating VM via API
@bryonadams Hello! I'm glad you finally managed to create your VM.
This message isn't very clear, I agree... In my opinion, it seems like you entered too many parameters for these endpoints, but I'll contact the XO team to improve this type of error message.
I'll also ask for information about the templates.If you encounter any other issues with the REST API related to VM creation, please feel free to report them in this thread.
-
RE: XOA license issue
@acebmxer Hello, the XO team is currently working on a solution. We will keep you inform as soon as it is on release.
-
RE: Xen Orchestra v6 - From Sources
@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!