Categories

  • All news regarding Xen and XCP-ng ecosystem

    144 Topics
    5k Posts
    rzrR
    We pushed the tested packages (of 3 batches) to the xcp-ng-updates repository, check blog post for summary and related advisories: https://xcp-ng.org/blog/2026/06/23/june-2026-updates-2-for-xcp-ng-8-3-lts/ Thanks everyone for the tests!

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    bleaderB
    @AlexanderK you could try to install perl-interpreter manually maybe? I happened to have a test host at hand that hasn't been updated since december, and the yum update went fine, perl interpreter was not installed before and yum update did install it on its own as a depency for openssl 3. Maybe others will have ideas as to why this would happen in your case.

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    BrantleyHobbsB
    Friends, I am once again here to make stupid mistakes so that you don't have to: it appears that the reason my backups were causing the machine to crash/hang is that: A) I was making DR replicas to local storage (the same device the host is booting from; not the same partition) B) I was filling it up. Again, this is not a production environment, simply a home lab, and I'm a bit resource poor, and I was looking for something other than my main disk repository for quick recovery. Making use of unused disk space left over on the boot device seemed like a Good Idea at the time. I added an additional physical disk specifically for DR replication and all my problems stopped. Hope that helps someone in the future.

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