Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    A
    Hello @igorglock, Damien is in holiday this week but he identified the issue and a patch should be tested for the next release of SM.

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    C
    Thanks for that information. I will make this message short because @stormi is busy but I want to say thanks to Vates and XCP-ng for all their work done to support Windows on the Xen platform. This includes TPM2 and secure boot support and Microsoft-signed pv drivers. Well done!

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    C
    @julienXOvates @julienXOvates said: @colomb said: I really miss the description column XO5 has in the default/home view. I understand space is limited for the tree view, but maybe it could appear when a host is selected in the tree view? In XO6, you will see it if you click on the eye at the end of the row, then on the right panel. Is this OK ? I noticed that. Unfortunately, for our use case, clicking on each vm to see the description is a little onerous. Ideally, you'd allow the user to customize the visible columns in the VMs page/tab. The fact that search includes description does help. Ultimately, it was convenient that XO5 would allow us to quickly identify vms by the description from the "Home" page.

  • Our hyperconverged storage solution

    47 Topics
    744 Posts
    M
    Hi @jonathon, If that happens again, could you show me the results of the command linstor n l (listing the nodes and their status) along with the version of each node? When restarting the controller, did you do it with a systemctl restart linstor-controller or with a systemctl stop linstor-controller, letting drbd-reactor elect a new node? You mentioned updating all of your nodes but you also mentioned rebooting only one node, is this correct? Depending on the version you were before the update it's possible that you got a version mismatch between your nodes (the satellites of each node + the controller needing to be rebooted so that they all get to the same version). The node appearing offline is due to a bug when updating from < linstor-server v1.32.0 to >= linstor-server v1.32.0 which makes the node with a different version appear as offline (the auth error is a symptom of that).

  • Non-English speakers

    34 Topics
    102 Posts
    B
    La remarque a été intégrée dans l'article: https://www.myprivatelab.tech/xcp_lab_v2_ha#perte-master Merci encore pour le retour.