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
    D
    @MajorP93 that’s fine - I never use ballooning anyway so I guess I am covered good

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    acebmxerA
    @MathieuRA Reverse proxy is npm. IP listed is of the new XO that was created. other then that no changes to the proxy. [image: 1779452871064-screenshot-2026-05-22-082629.png] [image: 1779452893128-screenshot-2026-05-22-082706.png] [image: 1779452941873-screenshot-2026-05-22-082853.png]

  • 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 !