Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    marcoiM
    @stormi said: We pushed the updates to the xcp-ng-updates repository: https://xcp-ng.org/blog/2026/05/21/may-2026-updates-3-for-xcp-ng-8-3-lts/ Changed since the initial announcement, xen was updated with the proper vulnerability fix and an update to sm was added to fix an issue on LVM-based SRs with CBT enabled. Thanks everyone for your feedback! update main pool. so far so good. updates went well and vms are running.

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    DanpD
    I'm not positive, but this may be available RSN in xo-lite.

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    acebmxerA
    Also note - when run a rebuild i get the following... [WARNING] XO 6 web UI (@xen-orchestra/web/dist) was not built — browser will use XO 5 UI at /v5. [WARNING] This may be caused by unmet peer dependencies (pinia 3.x, vue-router 5.x). [WARNING] Access your XO instance at: https://<host>/v5 until the upstream issue is resolved. The rebuild completed successfully. A few things to note from the output: Build successful: All 35 packages built in ~48 seconds XO 6 UI warning: @xen-orchestra/web was not built due to unmet peer dependencies (pinia ^3.0.1, vue@~3.5.13, vue-router ^5.0.0, vue-i18n ^11.1.2). The browser will use XO 5 at /v5 until upstream resolves this. Service running: HTTPS on port 443, tokens preserved, settings unchanged. The XO 6 UI issue is an upstream dependency mismatch in the master branch — nothing broken on your end. If you need XO 6, you'd need to wait for the upstream repo to update those peer deps or pin to a commit where they were satisfied.

  • Our hyperconverged storage solution

    47 Topics
    745 Posts
    J
    @Mathieu-L linstor n l was included in my original post. All nodes were updated to May 2026 Security and Maintenance Updates for XCP-ng 8.3 LTS, all nodes were restarted. May 2026 Updates #2 for XCP-ng 8.3 LTS was released, and a couple days later I installed on all hosts. No host restarted. When xen04 was restarted, that is when this issue happened. I had used systemctl restart linstor-controller here (https://xcp-ng.org/forum/post/105309) to restart the controller.

  • Non-English speakers

    35 Topics
    113 Posts
    olivierlambertO
    Ah excellente nouvelle Je passe le sujet en résolu !