Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    marcoiM
    went well with test systems. going to do prod soon.

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    O
    I have no idea what happened. I simply restarted my home server after some time and two out of the four VMs simply didn't start despite being configured to do so in XO-CE. I googled up some thread where someone suggested flipping the autostart setting off and on via the console, which I did, but the VMS still refuse to autostart. They do start manually just fine. I have also set every VM's autostart to disabled and then disabled the pool-wide autostart setting, rebooted the server, re-enabled everything, rebooted, and it's still not working Can anyone tell me what to do here, what to check? I don't really understand this system or Linux in general, everything I do is by copying what I find on internet or by trial and error. I literally changed nothing about the server and it's just not working all of a sudden

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    poddingueP
    I can't claim to know this part well, but the task name in your screenshot matches an older report, vatesfr/xen-orchestra#7496, where Importing content into VDI XO CloudConfigDrive also sat at 0% forever on XO from sources. In that one the host's self-signed certificate was being refused, and the only visible sign was a DEPTH_ZERO_SELF_SIGNED_CERT line next to importVdiContent in the xo-server log. Nothing showed in the UI at all. Since XOA works for you with the same cloud-config, how each one trusts the host certificate feels like a plausible place to look first, though I could be fully wrong about that. Could you check your xo-server output while one of those tasks is stuck and paste whatever importVdiContent line comes up, along with your commit number? If it reproduces on another host or a fresh build, that would make a solid GitHub issue, and a mention to @Team-XO-Backend might help in the meantime.

  • Our hyperconverged storage solution

    49 Topics
    790 Posts
    J
    All hosts are restarted with 9.2.18 loaded now. Will see what happens next. [15:56 ovbh-pprod-xen05 ~]# drbdadm --version DRBDADM_BUILDTAG=GIT-hash:\ 71c8bcff6ea77a022b272a7eba649a774251bac4\ build\ by\ @buildsystem\,\ 2025-11-03\ 10:21:36 DRBDADM_API_VERSION=2 DRBD_KERNEL_VERSION_CODE=0x090212 DRBD_KERNEL_VERSION=9.2.18 DRBDADM_VERSION_CODE=0x092100 DRBDADM_VERSION=9.33.0

  • Non-English speakers

    36 Topics
    117 Posts
    B
    Merci beaucoup pour vos retours ! @nathanael-h : C'est l'étape suivante !!! J'ai découvert cluster API le mois dernier et j'ai déja testé sur d'autres plateforme ! ça déchire !!! Je ne savais pas qu'il y avait un support de XCP-ng ! Je finis ma série d'article pour une installation classique et je bascule sur cluster API ! @ataxyanetwork Merci pour ton repo. Je vais regarder ça