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 mostly fixes, tools version update, a some improvements. Note: the previous batch 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 xen: Add support for xenpm get-core-temp to query CPU temperature on Intel platforms. Use xenpm get-core-temp to get the temperature on Intel's CPU, to fallback unsupported coretemp. Doc update being reviewed. grub: Sync with XenServer 8.4: Fix a rare out-of-memory error. dracut: Fixes Fix to force reboot/shutdown/halt. Fix issue where the omission of 'override' kernel modules from the initrd image could, in rare instances, prevent a freshly installed XCP-ng host from booting. Control Plane xapi: Update to 25.1.11, add fixes and improvements. Fixed an issue where a newly installed host wouldn't be able to join a pool due to incompatible features exposed by storage. Fix shutdown VMs not being migratable due to errors generated when the VM was running. Allow moving VMs back to DHCP from static IP with configure_ipv4/6. Network stunnel: Fixed stunnel only considering one of the self-signed certificates with the same DN. Tools xcp-ng-pv-tools: Update to XCP-ng Windows Guest Tools 9.1.200 (full changelog). Drivers mpi3mr-module: Update to version 8.17.1, adding newly supported SAS5116 devices. Optional: mellanox-mlnxen-alt: Fix build error with kernel 4.19.19-8.0.42.1+. Storage kmod-drbd: Update to 9.2.18 (full changelog) Improve XOSTOR stabilty when evacuating/evicting an host. xcp-ng-release-linstor: Relocate config file to v8.3-linstor repository. Versions dracut: 033-538.xcpng8.3 -> 033-539.1.xcpng8.3 gpumon: 24.1.0-84.1.xcpng8.3 -> 24.1.0-91.1.xcpng8.3 grub: 1:2.06-4.0.2.1.xcpng8.3 -> 1:2.06-4.0.5.1.xcpng8.3 mpi3mr-module: 8.6.1.0.0-1.xcpng8.3 -> 8.17.1.0.0-1.xcpng8.3 stunnel: 5.60-5.xcpng8.3 -> 5.60-6.1.xcpng8.3 xapi: 26.1.4-3.2.xcpng8.3 -> 26.1.11-1.1.xcpng8.3 xcp-featured: 1.2.1-1.xcpng8.3 -> 1.2.1-2.xcpng8.3 xcp-ng-pv-tools: 8.3-17.xcpng8.3 -> 8.3-18.xcpng8.3 xen: 4.17.6-9.1.xcpng8.3 -> 4.17.6-9.3.xcpng8.3 Optional packages: mellanox-mlnxen-alt: 5.4_1.0.3.0-2.xcpng8.3 -> 5.4_1.0.3.0-3.xcpng8.3 XOSTOR users: specific update procedure Some XOSTOR packages are provided in separate repository, and should be installed along xcp-ng regular packages, using the following commands: yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates,xcp-ng-linstor-testing yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates,xcp-ng-linstor-testing reboot Note: linstor packages themselves have not been updated, only kmod-drbd and xcp-ng-release-linstor. Thus, this time it's not necessary to restart the satellites before rebooting. The following XOSTOR-specific package received updates (and must be updated in the same transaction, which the above update commands will do): xcp-ng-release-linstor: 1.4-2.xcpng8.3 -> 1.5-1.xcpng8.3 (from xcp-ng-testing repo) kmod-drbd: 9.2.16-1.0.xcpng8.3 -> 9.2.18-2.0.xcpng8.3 (from xcp-ng-linstor-testing repo) 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 ~2 days We would like to thank users who reported feedback since our last call for testing: @Andrew, @XCP-ng-JustGreat, @acebmxer, @bufanda, @flakpyro, @jeffberntsen, @majorp93, @manilx, @marcoi, @ph7.
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    henri9813H
    Hello, Thanks for all !
  • 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 !