Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    5k Posts
    X
    Installed latest updates on my four host home lab pool and a fifth standalone host with no apparent issues.

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    olivierlambertO
    @jgrafton said: @laszlobortel We concluded that older Linux kernels plus live migrations plus lvmohba storage seems to trigger the issue. Our workaround was to upgrade to a mainline 6.x kernel packaged by ElRepo https://elrepo.org/wiki/doku.php?id=start for Rocky 8 systems that were especially prone to the CPU hang. The kernel upgrades effectively stopped the issue from occurring. That's ultra helpful interesting @jgrafton Maybe it's even worth a KB/known issue in our official doc, let me ping @thomas-dkmt I suppose https://docs.xcp-ng.org/troubleshooting/common-problems/ might be the right place to document it.

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    itservicesI
    Hi @pierrebrunet. I have deleted the "parentless" VDIs and snapshots. So the "Unhealthy VDI" page is empty for me. So everytime I retry with the VM in question it is creating a new (full) backup-chain. Regards, Marc

  • Our hyperconverged storage solution

    47 Topics
    755 Posts
    poddingueP
    Thanks for coming back to close it out. That's useful to know. So I was plenty wrong, as it was the XOSTOR licensing backend rather than the repo side I guessed at; those -32000 errors really don't give much away. For anyone landing here later: sounds like -32000 on XOSTOR creation can come from either end, a licensing/entitlement issue that support sorts, or a host not reaching the package repo, so both are worth checking. @alcoralcor, did support get yours sorted too, or is yours still the repodata / repo-reachability one? Glad you're unblocked either way.

  • Non-English speakers

    35 Topics
    113 Posts
    olivierlambertO
    Ah excellente nouvelle Je passe le sujet en résolu !