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

Hi @Kptainflintt,

I don't think this is related to XO6, but probably to this PR: https://github.com/vatesfr/xen-orchestra/pull/9231
VDIs with snapshot_of: <something> are now recognized as snapshots

spacotte-vates opened this pull request in vatesfr/xen-orchestra

closed fix(xo-server): improve handling of xapi snapshots #9231

ping @melissa-fr

@Pilow Hi.
I've managed to reproduce the issue. I'm currently investigating it

@wmazren Hi.
Weird,i am unable to reproduce the issue..

Can you show us the output from the following command?
xe vbd-param-list uuid=c6f4c7fa-4f6f-7999-d13c-3a29d887d828

@fluxtor Hi.

Could you try disabling the redirectToHttps option in your configuration?
This should resolve the issue. You can re-enable the option once the patch release 6.0.2 is available.
Alternatively, if you absolutely need this option, you can open a support tunnel so I can apply the fix directly to your XOA instance.

@fcgo Hi.
The OTP field is in the preferences property

E.g.

  {
    "email": "foo",
    "permission": "none",
    "pw_hash": "***obfuscated***",
    "preferences": {
      "otp": "<value>"
    },
    "groups": [],
    "id": "694e8856-04c9-448b-90ef-2beb96d119cb",
    "name": "foo",
    "href": "/rest/v0/users/694e8856-04c9-448b-90ef-2beb96d119cb"
  }

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

@MajorP93 I think I am finally able to reproduce the bug. I will try to fix it

@acebmxer
Perfect.
Thank you all as well! Early testing and feedback are very precious to us.

@acebmxer I want logs from the journalctl.
sudo systemctl restart xo-server
sudo journalctl -fu xo-server