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

Hi @Andrew.
This PR should fix your issue https://github.com/vatesfr/xen-orchestra/pull/8854

MathieuRA opened this pull request in vatesfr/xen-orchestra

closed fix(xo-server): fix incorrect state when remove server #8854

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

@MajorP93 can you try this branch? mra-fix-redirect-https It should fix your issue with redirectToHttps=true

Thank you all for your feedback!

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

@akihu2 Perfect, thanks.

Yes, you can close this topic

Here is the fix for the REST API + XO6
https://github.com/vatesfr/xen-orchestra/pull/9591

MathieuRA opened this pull request in vatesfr/xen-orchestra

closed fix(rest-api/xo6): cpu at VM creation was not working #9591

@akihu2 Hi.
It appears to be a bug, as the XO6 UI offers the option to choose the number of VCPU when creating a VM (obviously, this doesn't work).
I will fix this immediately.

Could you try disabling XO6?
In a configuration file, enable XO5 as the default version and ensure that XO6 is inaccessible (for example, by using an invalid path or removing the corresponding entry in the configuration). This will help determine if the issue is related to XO6/REST API.

https://docs.xen-orchestra.com/configuration#using-xo-5-as-the-default-interface

Hi @acebmxer the bug related to the ISO will be fixed soon (probably tomorrow on the master branch).
@gheppy Same for the CPU provisioning bug.

@ElFritto Can you try this branch xo6/update-site-dashboard and check if that solve your issue?

Perfect, thanks.
We will fix the infinite loader for backups info soon

I don't understand what's happening.
Could you try installing directly from the xen-orchestra GitHub repository? This would help us determine if the problem is with the ronivay installation script.
Could you also show us your xo server config?

Do you confirm that you are using an admin user?

Hi @elfritto

Personally, I have no issues with XS pools.
Can you provide more information?

• Do you have any error logs on xo server?
• Are there any errors in your browser console?
• Is your're XO up to date?