XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    • Profile
    • Following 0
    • Followers 1
    • Topics 0
    • Shares 0
    • Posts 147
    • Groups 4
    gduperreyG Offline
    1. Home
    2. gduperrey

    gduperrey

    @gduperrey

    Vates 🪐 XCP-ng Team

    Stormi's helper.
    Science-Fiction and Fantasy lover. Love books, comics, animes...

    213
    Reputation
    50
    Profile views
    147
    Posts
    1
    Followers
    0
    Following
    Joined
    Last Online

    gduperrey Unfollow Follow
    OS Platform & Release Team Vates 🪐 XCP-ng Team Admin
    • RE: XCP-ng 8.3 updates announcements and testing

      The storage and XAPI teams are currently investigating the issues that have been reported.

      There is no final solution yet, but we are getting closer. Unfortunately, there is no ETA at this time.

      Thank you very much for all your testing and feedback! 🙂

      posted in News
      gduperreyG
      gduperrey
    • RE: Epyc VM to VM networking slow

      The fix, which was proposed as a test to resolve some of the issues encountered, has been integrated into an official update candidate which will be released to everyone next time we publish updates. For more information on this update, you can consult the following post: https://xcp-ng.org/forum/post/96135

      posted in Compute
      gduperreyG
      gduperrey
    • RE: High Fan Speed Issue on Lenovo ThinkSystem Servers

      The kernel RPM integrating the patch is now available on the xcp-ng-testing repo. So you can already upgrade and use it. To do this, here are the commands:

      yum clean metadata --enablerepo=xcp-ng-testing
      yum update kernel --enablerepo=xcp-ng-testing
      reboot
      

      It will be released to all our users in an upcoming security update or update train. We don't have a date yet.

      posted in Hardware
      gduperreyG
      gduperrey
    • RE: XCP-ng 8.3 updates announcements and testing

      Updates published: https://xcp-ng.org/blog/2025/07/03/july-2025-security-and-maintenance-update-for-xcp-ng-8-3-lts/

      Thank you for the tests!

      posted in News
      gduperreyG
      gduperrey
    • RE: XCP-ng 8.2 updates announcements and testing

      New update candidates for you to test!

      As you may know, we group non-urgent updates together for a collective release, in order not to cause unnecessary maintenance for our users.

      The moment to release such a batch has come, so here they are, ready for user tests before the final release.

      • XAPI:
        • Synced with XS82ECU1074
          • Enhancement: robustification of the command xe host-emergency-ha-disable
          • Correction of different issues:
            • Performing a hard shutdown of a VM may hang due to unnecessary RBCA permission checks. An icon (yellow triangle) may then be displayed on some management applications, indicating that the shutdown process did not complete successfully.
            • Canceling a hard shutdown of a hung VM fails because the cancel function only checks for proper shutdowns.
            • Migrating VMs from 8.2.1 to 8.3 with the xe vm-migrate command may fail with the error 'Failure: Unknown tag/contents'.
            • You may encounter a 500 error (internal server error) when trying to retrieve RRD measurements from a powered off virtual machine.
      • xsconsole:
        • Synced with XS82ECU1074: Fix for a time-out when creating an iSCSI SR.
      • guest-templates-json:
        • Add generic templates for Linux BIOS and UEFI
        • Synced with XS82ECU1085:
          • Oracle 8 requires minimum 2 vCPUS.
          • Added template for Ubuntu 24.04
      • sm:
        • Synced with XS82ECU1075
          • Updated multipath.conf for several SANs
          • Fix for CA-393194: Find the real PV in a VG before removing the VG.
      • blktap: Synced with XS82ECU1075: Improvements on coalesce performance.
      • curl: Backport fixes for several CVE: CVE-2024-2004, CVE-2024-2379, CVE-2024-2398, CVE-2024-2466, CVE-2024-6197, CVE-2024-7264
      • openssl: Update to version 1.0.2k-26 from CentOS 7 updates and backports of available CVE fixes from openssl upstream. Update from CentOS 7 Includes fixes for CVE-2021-3712, CVE-2022-2078 and CVE-2023-0286. Backport are fixing CVE-2019-1547, CVE-2019-1551 and CVE-2019-1563.
      • xs-openssl: Rebased on version 1.1.1k-12 from CentOS 8 Stream. Include fixes for CVE-2023-5678, CVE-2023-3446, CVE-2023-3817 and a proper fix for CVE-2020-25659.
      • zstd: Update to version 1.5.5 to avoid an extremely rare cases of corruption
      • xcp-ng-xapi-plugins: Enhance error reporting when a command run on a host fails.
      • xenserver-status-report: Update to latest version, synced with XS82ECU1058
      • python-defusedxml: Added as a new dependency of xenserver-status-report.
      • Alternate Drivers: Updated to newer versions.
        • intel-i40e-alt: From version 2.22.20-3.1 to 2.22.20-5.1
        • mellanox-mlnxen-alt: From version 5.9.0.5.5.0-1.1 to 5.9.0.5.5.0-1.2
        • More information about drivers and current versions is on the drivers page: (https://github.com/xcp-ng/xcp/wiki/Drivers).
      • New alternate driver mlx4-modules-alt: To resolve some issues with CX3 cards and SR-IOV, we added an updated version 4.9-7.1.0.0-LTS of this driver.
      • kernel-alt: Backport of a fix to correct cooling fan rotation speed on some Lenovo servers. For more information, you can read this thread on the forum.

      As a dependency of XOSTOR:

      • http-nbd-transfer:
        • Try to open device and start HTTP server before notifying the user
        • Install pyc and pyo files

      Test on XCP-ng 8.2

      From an up to date host:

      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.

      Versions

      • blktap: 3.37.4-4.1.xcpng8.2
      • curl: 8.6.0-2.2.xcpng8.2
      • forkexecd: 1.18.3-12.1.xcpng8.2
      • gpumon: 0.18.0-20.1.xcpng8.2
      • guest-templates-json: 1.10.7-1.2.xcpng8.2
      • http-nbd-transfer: 1.4.0-1.xcpng8.2
      • message-switch: 1.23.2-19.1.xcpng8.2
      • ocaml-rrd-transport: 1.16.1-17.1.xcpng8.2
      • ocaml-rrdd-plugin: 1.9.1-17.1.xcpng8.2
      • ocaml-tapctl: 1.5.1-17.1.xcpng8.2
      • ocaml-xcp-idl: 1.96.7-6.1.xcpng8.2
      • ocaml-xen-api-client: 1.9.0-20.1.xcpng8.2
      • ocaml-xen-api-libs-transitional: 2.25.7-1.1.xcpng8.2
      • openssl: 1.0.2k-26.2.xcpng8.2
      • python-defusedxml: 0.7.1-1.xcpng8.2
      • rrd2csv: 1.2.6-17.1.xcpng8.2
      • rrdd-plugins: 1.10.9-14.1.xcpng8.2
      • sm: 2.30.8-13.1.xcpng8.2
      • sm-cli: 0.23.0-63.1.xcpng8.2
      • squeezed: 0.27.0-20.1.xcpng8.2
      • varstored-guard: 0.6.2-17.xcpng8.2
      • vhd-tool: 0.43.0-20.1.xcpng8.2
      • wsproxy: 1.12.0-21.xcpng8.2
      • xapi: 1.249.38-1.11.xcpng8.2
      • xapi-nbd: 1.11.0-19.1.xcpng8.2
      • xapi-storage: 11.19.0_sxm2-19.xcpng8.2
      • xapi-storage-script: 0.34.1-18.1.xcpng8.2
      • xcp-networkd: 0.56.2-17.xcpng8.2
      • xcp-rrdd: 1.33.4-6.1.xcpng8.2
      • xenopsd: 0.150.19-5.1.xcpng8.2
      • xenserver-status-report: 1.3.16-3.xcpng8.2
      • xcp-ng-xapi-plugins: 1.10.1-1.xcpng8.2
      • xs-opam-repo: 6.35.13-4.xcpng8.2
      • xs-openssl: 1.1.1k-12.3.xcpng8.2
      • xsconsole: 10.1.13.1-2.1.xcpng8.2
      • zstd: 1.5.5-1.el7

      Optional packages:

      • kernel-alt: 4.19.265-2.xcpng8.2
      • Alternates drivers:
        • intel-i40e-alt: 2.22.20-5.1.xcpng8.2
        • mellanox-mlnxen-alt: 5.9_0.5.5.0-1.2.xcpng8.2

      New optional package:

      • mlx4-modules-alt: 4.9_7.1.0.0-1.xcpng8.2

      What to test

      Normal use and anything else you want to test. The closer to your actual use of XCP-ng, the better.

      Test window before official release of the updates

      ~1 week.

      posted in News
      gduperreyG
      gduperrey
    • RE: XCP-ng 8.2 updates announcements and testing

      The update is published. Thanks for your tests!
      Blog post: https://xcp-ng.org/blog/2022/11/04/november-2022-security-update/

      posted in News
      gduperreyG
      gduperrey
    • RE: XCP-ng 8.3 updates announcements and testing

      New update candidate for you to test!

      A new update for the Xen packages is ready, which brings a significant improvement in live migration performance on AMD systems under heavy load, that we add to the previous batch of updates for a common publication.


      Maintenance updates

      • xen: Improve migration performance on AMD systems under heavy load.

      Test on XCP-ng 8.3

      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.

      Versions:

      • xen: 4.17.6-4.1.xcpng8.3

      What to test

      Normal use and anything else you want to test. If you have a pool with AMD processors, we're interested in your feedback regarding live migration under heavy load.

      Test window before official release of the updates

      ~4/5 days

      posted in News
      gduperreyG
      gduperrey
    • RE: RPM package vmfs6-tools missing for local migration procedure

      Hello,

      We've added a card to our backlog to investigate this topic.

      posted in Migrate to XCP-ng
      gduperreyG
      gduperrey
    • RE: XCP-ng 8.3 updates announcements and testing

      Update published: https://xcp-ng.org/blog/2025/01/23/january-2025-maintenance-update-for-xcp-ng-8-3/

      Thank you for the tests!

      posted in News
      gduperreyG
      gduperrey
    • RE: XCP-ng 8.3 updates announcements and testing

      New update candidates for you to test!

      A new batch of non-urgent updates is ready for user tests before a future collective release. Below are the details about these.

      • amd-microcode: Update AMD microcode to the 2024-11-21 drop
        • Updates firmware for families 17h and 19h CPUs. For the first time, AMD published updates for non-server CPUs. One can assume that they started supporting microcode update for these, contrarily to what they did in the past, and that these updates thus fix various bugs and vulnerabilities. This is only (sensible) speculation at the moment, though.
      • grub: Backport VLAN networking support for UEFI PXE boot.
      • iperf3: Upgrade to version 3.9-13 from CentOS 7
        • Includes a security fix for CVE-2023-38403
      • kernel: Backport of a fix to correct cooling fan rotation speed on some Lenovo servers. For more information, you can read this thread on the forum.
      • kexec-tools: Backport of a patch removing kernel_version(). Fixing a bug for kernel with a patchlevel greater than 255.
      • netdata: Fixed an issue that could occur when quickly uninstalling the package, right after an unfinished installation, and leave a service in an undetermined status.
      • slang: Fixed display and input issues in optional package mc.
      • sm: Contains a fix for leaf coalesce where the size of the leaf to coalesce was wrongly computed before deciding if it was a live coalesce or not, it resulted in some leaf having too much data to coalesce not successing the live coalesce and staying in this state indefinitely.
      • xapi:
        • Fixed a malfunction related to the absence of a certificate, which could cause a loop.
        • Fixed and improved various points in IPv6, related to management, reboot and re-initialization.
      • xo-lite: Update to version 0.6.0. For more details, you can consult the blog post on the latest release of Xen Orchestra.

      Optional packages:

      • kernel-alt: Backport of a fix to correct cooling fan rotation speed on some Lenovo servers. For more information, you can read this thread on the forum.
      • socat: Update the package to version 1.7.4.1 which includes a fix for a buffer overflow and security fixes.
      • traceroute: Updated to version 2.1.5.
      • Alternate Drivers: Updated to newer versions.
        • broadcom-bnxt-en-alt: From version 1.10.2_227.0.130.0 to 1.10.3_231.0.162.0
        • intel-i40e-alt: From version 2.22.20-3.1 to 2.26.8
        • More information about drivers and current versions is on the drivers page: (https://github.com/xcp-ng/xcp/wiki/Drivers).

      Test on XCP-ng 8.3

      From an up-to-date host:

      yum clean metadata --enablerepo=xcp-ng-testing
      yum update --enablerepo=xcp-ng-testing
      reboot
      

      The usual update rules apply: pool coordinator first, etc.

      Versions

      • amd-microcode: 20240503-1.1.xcpng8.3
      • grub: 2.06-4.0.2.1.xcpng8.3
      • iperf3: 3.9-13.xcpng8.3
      • kernel: 4.19.19-8.0.37.1.xcpng8.3
      • kexec-tools: 2.0.15-20.1.xcpng8.3
      • netdata: 1.44.3-1.2.xcpng8.3
      • slang: 2.3.2-11.xcpng8.3
      • sm: 3.2.3-1.13.xcpng8.3
      • xapi: 24.19.2-1.9.xcpng8.3
      • xo-lite: 0.6.0-1.xcpng8.3

      Optional packages:

      • kernel-alt: 4.19.322+1-1.xcpng8.3
      • socat: 1.7.4.1-6.xcpng8.3
      • traceroute: 2.1.5-2.xcpng8.3
      • Alternate drivers:
        • broadcom-bnxt-en-alt: 1.10.3_231.0.162.0-1.xcpng8.3
        • intel-i40e-alt: 2.26.8-1.xcpng8.3

      What to test

      Normal use and anything else you want to test. The closer to your actual use of XCP-ng, the better.

      Test window before official release of the updates

      None defined, but early feedback is always better than late feedback, which is in turn better than no feedback 🙂

      posted in News
      gduperreyG
      gduperrey
    • RE: XCP-ng 8.3 updates announcements and testing

      Updates are live now

      Thank you everyone for your tests and your feedback!

      This includes updates that you have tested, as well as security updates that were under embargo.

      Check out the blog post for the full list of fixes and any post-update steps: https://xcp-ng.org/blog/2026/11/10/november-2026-security-updates-3-for-xcp-ng-8-3-lts/

      If you installed the kernel from our last call for testing, please read on. You can check with rpm -q kernel.

      The released kernel is not the 4.19.19-8.0.49.3 you tested, but 4.19.19-8.0.46.16. Its release number is lower, so a regular update will leave your hosts on 4.19.19-8.0.49.3. We identified some issues in 4.19.19-8.0.49.3.

      To downgrade and install kernel-4.19.19-8.0.46.16, run the following commands:

      yum clean metadata
      yum downgrade --setopt=protected_packages= kernel-4.19.19-8.0.46.16.xcpng8.3
      yum update
      reboot
      

      The usual update rules apply: pool coordinator first, etc.

      We expect to release a new kernel in a few days, and it will install as a normal update from either version.

      posted in News
      gduperreyG
      gduperrey
    • RE: XCP-ng 8.3 updates announcements and testing

      @manilx

      If we could have waited, we would have. However, the xen security update released yesterday, given its critical nature, did not allow for that.

      Please rest assured that we are aware of this issue and are doing our utmost to keep the number of releases to a minimum. We are also discussing how to communicate regarding the most critical updates and how to limit the need for reboots.

      posted in News
      gduperreyG
      gduperrey
    • RE: XCP-ng 8.3 updates announcements and testing

      @MajorP93

      We discussed your feedback yesterday, but we don't have an explanation at the moment. Our Windows expert tried to reproduce the behavior but was unable to trigger this error.

      Furthermore, we haven't encountered any issues on our end with the RPU (Rolling Pool Update) operations performed during our tests, whether done manually or via XO. It is possible, however, that we are missing the specific scenario (VMs or configuration) required to trigger this one.

      Have you been able to find any further information in the host logs?

      If not, could you export and send us a status report using xen-bugtool? Perhaps one of our developers will be able to spot something in it that helps explain the issue.

      posted in News
      gduperreyG
      gduperrey
    • RE: XCP-ng 8.3 updates announcements and testing

      @acebmxer said:

      Conclusion:
      Network layout config problems, buffer overflows, or silent packet drops are 100% ruled out here (all hardware discards are flat zero).

      This wasn't a user mistake or an accidental configuration mismatch. The new sm or blktap components hit a deep kernel lockup handling the multi-stream VHD storage exports. The file locks deadlocked the kernel handles so badly that the hosts ignored standard and low-level CLI commands entirely, forcing a hard out-of-band physical power cycle of the XCP-ng hosts and the TrueNAS storage server just to clear the uninterruptible I/O sleep queue.

      I haven't touched a thing since getting the hardware back up and verifying what choked. The system is sitting exactly as it is right now. Let me know what specific debugging paths you want me to look at or what logs you need from that window to trace this down.

      @storage could someone please take a look and help analyze this issue?

      posted in News
      gduperreyG
      gduperrey
    • RE: XCP-ng 8.3 updates announcements and testing

      The storage and XAPI teams are currently investigating the issues that have been reported.

      There is no final solution yet, but we are getting closer. Unfortunately, there is no ETA at this time.

      Thank you very much for all your testing and feedback! 🙂

      posted in News
      gduperreyG
      gduperrey
    • RE: XCP-ng 8.3 updates announcements and testing

      We have just released security updates for xen and blktap. Full details are available on the blog: https://xcp-ng.org/blog/2026/10/13/october-2026-security-updates-2-for-xcp-ng-8-3-lts/

      posted in News
      gduperreyG
      gduperrey
    • RE: Timezone updates for tzdata 2026e

      Hello,

      We have received your request and thank you for the feedback on this matter.

      A task card has been created and assigned to one of our teams. It has not yet been assigned to a specific developer, but we will be sure to get back to you once it has been addressed and resolved.

      posted in XCP-ng
      gduperreyG
      gduperrey
    • RE: XCP-ng 8.3 updates announcements and testing

      Thank you everyone for your tests and your feedback!

      The updates are live now: https://xcp-ng.org/blog/2026/10/05/october-2026-updates-1-for-xcp-ng-8-3-lts/

      We decided not to release the xen update that was initially included in the testing phase of this update cycle. It introduced changes related to support for Windows VMs with more than 64 vCPUs; a feature that is not yet fully supported and requires further work to be completely implemented.

      We therefore chose to postpone it to avoid any regressions or user confusion, aiming to release a properly finalized and documented version in the near future.

      This version should have no impact on your test environments, and they can continue to operate as is. Any future xen update should have a higher version number and should install over the current one.

      However, if you do not wish to keep this update on your test environments, you can downgrade using the command yum downgrade xen-*.

      posted in News
      gduperreyG
      gduperrey
    • RE: XCP-ng 8.3 updates announcements and testing

      We have just released security updates for xen and blktap. Full details are available on the blog: https://xcp-ng.org/blog/2026/09/08/september-2026-security-updates-1-for-xcp-ng-8-3-lts/

      posted in News
      gduperreyG
      gduperrey
    • RE: XCP-ng 8.3 updates announcements and testing

      Hello @XCP-ng-JustGreat,

      I cannot comment on RPU issues via XO. I would recommend creating a new topic to report the problem directly to the XO team so they can analyze it.

      As you can see, we recommend validating updates via the command line directly on XCP-ng before releasing them. That is a different scenario.

      However, if several of you are experiencing RPU issues with XO, a dedicated topic will allow that team to investigate the situation and consult other teams if necessary. This would ensure the issue is better addressed and analyzed 🙂

      posted in News
      gduperreyG
      gduperrey