Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    rzrR
    @ph7 said: @rzr XO-lite was already on 0.21.0 (13f98) after the update 2 weeks ago.. Don't know if it's the same. yes it's same landed in testing before and not yet moved to updates, btw this version does not bring much change as it's a rebuild with dep update, see there is no full changelog : https://github.com/vatesfr/xen-orchestra/releases/tag/xo-lite-v0.21.0

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    julienXOvatesJ
    Hi @mdm, Here is the response from a SME 1- XO get the VM metadata through soap api and create the vm /network XO use the nbdkit + nbdkit-vddk package , connecting to each disk XO connect through NBD to nbdkit XO list the allocated blocks XO create the disk XO read the block and import the data into the disk (though a vhd or qcow2 stream depending on the size) 2- though XO. There is a lot of disk transform occuring here 3- not anymore, it was too brittle, especially on when the disk are locked or not. Also it was not scaling too well 4- see 3- + vddk transfer is overwhelmly faster that previous access through http, is compatible with VSAN and don't lock the disks. (+ also see https://xen-orchestra.com/blog/xen-orchestra-5-110/ section "VMware to Vates (V2V)" where we made key improvements)

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    simonpS
    @acebmxer Ok thanks. I'm guessing that switching to node 22 solved the dist issue but you still have the Redis issue. We have identified a possible problem with Redis that looks like your issue, would you mind checking out this branch fix_redis_orphaned_entry ? Try loading the v6 dashboard again after a rebuild and restart of your XO. Thank for your help.

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