Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    stormiS
    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!

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    F
    @DustinB In my case, the XO Community installation is itself a VM on XCP-NG. I just want a safety net in case an update to my XO install goes haywire. Instead of relying on snapshots of XO I've just been cloning the XO VM instance monthly, and running XO updates using ronivay's script weekly. So far it's been smooth sailing- just doing my due diligence in case anything hits the fan.

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    R
    @Greg_E Would you know the version of the installed xen tools?

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