Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    A
    @stormi I'm also getting error on some VMs while trying to export a disk and also trying to even start some VMs from NFS (that were fine before). xo-server[565]: 2026-05-13T02:53:15.746Z xo:api WARN admin | vm.start(...) [2s] =!> XapiError: INTERNAL_ERROR(xenopsd internal error: Storage_error ([S(Illegal_transition);[[S(Activated);S(RO)];[S(Activated);S(RW)]]])) xo-server[565]: 2026-05-13T02:53:40.652Z xo:api WARN admin | vm.start(...) [3s] =!> XapiError: SR_BACKEND_FAILURE_46(, The VDI is not available [opterr=VDI 399734eb-5965-4799-ac36-f6dd774db867 not detached cleanly], )

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    maximsachsM
    Hi @yannsionneau, have you had the time to investigate this issue some more? We would love to hear if there is already a solution.

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    J
    ping @poddingue for visibility as I believe I've found the trigger for IPv6 expanding... Live Migrations

  • 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
    108 Posts
    semarieS
    Bonjour, Apparemment, la valeur vient de la xapi : $ xe host-list params=uuid,software-version uuid ( RO) : 9940971b-45f6-4225-aaef-ddb0668e3734 software-version (MRO): product_version: 8.3.0; product_version_text: 8.3; product_version_text_short: 8.3; platform_name: XCP; platform_version: 3.4.0; product_brand: XCP-ng; xapi: 26.1; build_number: 8.3.0; git_id: 3; hostname: localhost; date: 20260430T09:28:41Z; dbv: 0.0.1; xapi_build: 26.1.3; xen: 4.17.6-6; linux: 4.19.0+1; xencenter_min: 2.21; xencenter_max: 2.21; network_backend: openvswitch; db_schema: 5.793 uuid ( RO) : 5f16a481-103e-4ca8-a0e2-b708d2c26437 software-version (MRO): product_version: 8.3.0; product_version_text: 8.3; product_version_text_short: 8.3; platform_name: XCP; platform_version: 3.4.0; product_brand: XCP-ng; xapi: 26.1; build_number: 8.3.0; git_id: 3; hostname: localhost; date: 20260430T09:28:41Z; dbv: 0.0.1; xapi_build: 26.1.3; xen: 4.17.6-6; linux: 4.19.0+1; xencenter_min: 2.21; xencenter_max: 2.21; network_backend: openvswitch; db_schema: 5.793 qui prend l'information depuis le fichier /etc/xensource-inventory (sur le host): # grep BUILD_NUMBER /etc/xensource-inventory BUILD_NUMBER='8.3.0' Ce fichier est mis à jour par le script de post-config du package rpm xcp-ng-release (voir le script utilisé ici) La valeur a été mise à jour la dernière fois en 2023 (voir le changelog pour 8.3.0-13). La valeur acutelle est définie dans la variable BUILD_NUMBER rpm variable du package. Cela veut dire que le host avec Build number = cloud ne semble pas à jour ? Pouvez-vous vérifier la version installée du package xcp-ng-release, en utilisant la commande rpm -q xcp-ng-release ?