Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    5k Posts
    rzrR
    New maintenance update candidates for XCP-ng 8.3 LTS This release batch contains fixes, and a security fix on an optional package, Note: the two previous batches of updates has not been released yet, so if you haven't tested it, you will see more updates than described here when you'll install the update candidates. Refer to the previous announcements. What changed Virtualization & System kexec-tools: Update to sync with Xen Server: Add checks to reboot a crashed host if kernel crash handling doesn't complete. Control Plane xapi: Fix the VM revert regression introduced in earlier "testing" version. Optional package lldpd: Fix CVE-2026-46433, a buffer over-read when processing the "VLAN tags from an Ethernet frame. Versions kexec-tools: 2.0.15-20.1.xcp-ng8.3 -> kexec-tools-2.0.15-21.1.xcpng8.3 xapi: 26.1.11-1.1.xcpng8.3 -> xapi-26.1.11-1.2.xcpng8.3 Optional packages: lldpd: 1.0.4-1.1.xcpng8.3 -> 1.0.4-1.2.xcpng8.3 Test on XCP-ng 8.3 Warning: XOSTOR users should skip this part and follow the instructions of the previous section. yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates reboot The usual update rules apply: pool coordinator first, etc. What to test As usual, normal use and anything else you want to test. Test window before official release of the updates ~1 day We would like to thank users who reported feedback since our last call for testing: @Andrew, @ScarfAntennae, @XCP-ng-JustGreat, @acebmxer, @bufanda, @flakpyro
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    E
    @tuxen Doing some research, it doesn't look like the Xeon's I have are affected. But I'm willing to try the next time I need to reboot. Will report back after that.
  • 3k Topics
    28k Posts
    itservicesI
    Quick Update: Was looking good with commit cf26d. After the transfer completed the VDI of that particular VM was still in use, according to XO. So still failure on the job. 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.
  • 35 Topics
    113 Posts
    olivierlambertO
    Ah excellente nouvelle Je passe le sujet en résolu !