I will create a card for this feature request to discuss with the whole XO team. I will keep you updated here

Hi @irtaza9
You have a typo in your vm-templates URL.
fields instead of field

Hi @irtaza9
FYI, for about 2 years, VMs expose a creation field:

"creation": {
    "date": string,
    "template": string,
    "user": string
  },

With this you can filter VMs by creation.user to list only VMs created by a user.
/rest/v0/vms?filter=creation:user:<user-id>

Hi.
The IPMI plugin is only used to display hardware information if you are using mona_1.44gg.

To display if a BIOS update is available, we mainly fetch this endpoint: https://pictures.2cr.si/Images_site_web_Odoo/Pages_produit/VATES-BIOS_BMC_last-version.json

Does your host have access to this endpoint?
What is the ouput of xo-cli host.getBiosInfo id=<host-id>

Hi,
Since XO is a client, I don't think it's a good idea to have this kind of feature. In this case, a VM could be restarted from sources other than XO, and would not apply the new VDI size.

However, I believe we can handle this situation by implementing a modal that appears when editing the VDI size of a running VM. This modal can offer the option to restart the VM immediately and apply the changes. In my opinion, removing the "pending" state will prevent confusion

@ashinobi Several bug fixes related to VM migration are on the xo5/fix-bulk-migration branch. Could you please test to see if they solve your issue?

While investigating the code, I found something unexpected. We don't have exactly the same behavior for migrating from the Home/VM view and from the VM view itself.
I will try to fix this and it might solve your problem.
I will come back to you when I have opened the branch to allow you to do some tests on it.

I see that the bug is actually already fixed on the latest version (5.98.1).

Hi @TwoPlus1, thanks for the report. I can reproduce the bug. We will fix this for the next release (5.99)`

FYI, we have added this feature to our backlog

This is normal, as the tasks endpoints are in the old REST API (undocumented by Swagger).
We are gradually migrating to the new REST API to document all endpoints.

Hello @DevFlint.
/rest/v0/tasks/:id exists. It's not yet documented in Swagger, but it does exist.

FYI, "actions" endpoint are specific.
They can be executed asynchronously (which is what you're currently doing). In this case, a task is returned and needs to be monitored. Use /rest/v0/tasks/:id for this.
You can also execute your action synchronously by using sync=true as a query parameter. In this case, the VM ID will be returned in response.

This should normally be documented in Swagger. If it's not clear in the documentation, we can improve it

PR: https://github.com/vatesfr/xen-orchestra/pull/8599

MathieuRA opened this pull request in vatesfr/xen-orchestra

closed fix(xo-server/xen-server): fix disabling an enabled but disconnected server #8599

Hi, I will fix it ASAP. Thanks

@hanzzz This PR adds the ability to run a schedule. So, a temporary workaround is to create a job, create a schedule for this job, then run your schedule.

If you are not using XO from source, you will have to wait for version 5.106

Hi.
I confirm that no actions are currently available for hosts.

Hi @eeldivad

You can use the json flag. xo-cli rest --json get vdis

Hi @irtaza9
You have a typo in your vm-templates URL.
fields instead of field

Hi @irtaza9.
The REST API is only available for admin users.
It is planned to handle other types of users in a few months

@irtaza9 you need to use the user-id, not the username