Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    5k Posts
    acebmxerA
    @rzr I also installed updates this morning no new issues to report.

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    jgraftonJ
    @laszlobortel We never reached a definitive root cause and did end up fully migrating to XCP-NG from VMware. We still have roughly 100 VMs running Rocky 8.10. The 4.18.0-553.94.1 kernels and above don't seem to have the same CPU issues but I'm not sure if that's because a kernel bug was mitigated or because we upgraded our backend storage to all flash arrays (Pure Storage C50's). The CPU still gets pegged on a Rocky 8 VM every once in a blue moon but not often enough to warrant more time being spent tracking it down.

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    itservicesI
    Problem still persists with commit e9b66. Thanks for the support! 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 !