XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. stormi
    Offline
    • Profile
    • Following 0
    • Followers 17
    • Topics 40
    • Posts 1,401
    • Groups 6

    stormi

    @stormi

    Vates 🪐 XCP-ng Team
    1.1k
    Reputation
    2.3k
    Profile views
    1.4k
    Posts
    17
    Followers
    0
    Following
    Joined
    Last Online
    Location Lyon

    stormi Unfollow Follow
    Lead Maintainer OS Platform & Release Team Vates 🪐 XCP-ng Team Global Moderator Admin

    Best posts made by stormi

    • XCP-ng 8.0.0 Beta now available!

      Good morning, afternoon, evening or night to everybody.

      The beta release of XCP-ng 8.0 is available right now 🚀 .

      What's new

      • Based on Citrix Hypervisor 8.0 (see https://xen-orchestra.com/blog/xenserver-7-6/).
      • New kernel (4.19), updated CentOS packages (7.2 => 7.5)
      • Xen 4.11
      • New hardware supported thanks to the new kernel. Some older hardware is not supported anymore. It's still expected work in most cases but security cannot be guaranteed for those especially against side-channel attacks on legacy Intel CPUs. See Citrix's Hardware Compatibility List. Note: in 7.6 we've started providing alternate drivers for some hardware. That's something we intend to keep doing, so that we can extend the compatibility list whenever possible. See https://github.com/xcp-ng/xcp/wiki/Kernel-modules-policy.
      • ). Note: in 7.6 we've started providing alternate drivers
      • Experimental UEFI support for guests (not tested yet: have fun and report!)
      • An updated welcome HTML page with the ability to install Xen Orchestra Appliance directly from there (see below). Tell us how it works for you and what you think of it!
      • A new implementation of the infamous emu-manager, rewritten in C. Test live migrations extensively!
      • Mirrors: you can offer mirrors and yum now pulls from them: https://github.com/xcp-ng/xcp/wiki/Mirrors
      • Already includes the latest patches for MDS attacks.
      • The net-install installer now checks the signature of the downloaded RPMs against our GPG key, which is becoming more important now that we're delegating downloads to mirrors.
      • Status of our experimental packages:
        • ext4 and xfs support for local SR are still considered experimental, although no one reported any issue about it. You still need to install an additional package for it to work: yum install sm-additional-drivers.
        • ZFS packages are now available in the main repositories, can be installed with a simple yum install zfs, and have been updated to version 0.8.1 (as of 2019-06-18) which removes the limitations we had with the previous version in XCP-ng 7.6.
        • No more modified qemu-dp for Ceph support, due to stalled issue in 7.6 (patches need to be updated). However the newer kernel brings better support for Ceph and there's some documentation in the wiki: https://github.com/xcp-ng/xcp/wiki/Ceph-on-XCP-ng-7.5-or-later.
        • Alternate kernel: none available yet for 8.0, but it's likely that we'll provide one later.
      • New repository structure. updates_testing, extras and extras_testing disappear and there's now simply: base, updatesandtesting`. Extra packages are now in the same repos as the main packages, for simpler installation and upgrades.
      • It's our first release with close to 100% of the packages rebuilt in our build infrastructure, which is Koji: https://koji.xcp-ng.org. Getting to this stage was a long path, so even if it changes nothing for users it's a big step for us. For the curious ones, more about the build process at https://github.com/xcp-ng/xcp/wiki/Development-process-tour.

      Documentation

      At this stage you should be aware that our main documentation is in our wiki and you should also know that you can all take part in completing it. Since the previous release, it has improved a lot but there's still a lot to improve.

      How to upgrade

      As usual, there should be two different upgrade methods: classical upgrade via installation ISO or upgrade using yum.

      However, the yum-style update is not ready yet. Since this is a major release, Citrix does not support updating using an update ISO, and the consequence for us is that the RPMs have not been carefully crafted for clean update. So it's all on us, and we plan to have this ready for the RC (release candidate).

      Before upgrading, remember that it is a pre-release, so the risks are higher than with a final release. But if you can take the risk, please do and tell us how it went and what method you used! However, we've been testing it internally with success and xcp-ng.org already runs on XCP-ng 8.0 (which includes this forum, the main repository and the mirror redirector) !

      Although not updated yet, the Upgrade Howto remains mostly valid (except the part about yum-style upgrade, as I said above).

      • Standard ISO: http://mirrors.xcp-ng.org/isos/8.0/xcp-ng-8.0.0-beta.iso
      • Net-install ISO: http://mirrors.xcp-ng.org/isos/8.0/xcp-ng-8.0.0-netinstall-beta.iso
        • Do not use the pre-filled URL which still points at XCP-ng 7.6. Use this instead: http://mirrors.xcp-ng.org/netinstall/8.0
      • SHA256SUMS: http://mirrors.xcp-ng.org/isos/8.0/SHA256SUMS
      • Signatures of the sums: http://mirrors.xcp-ng.org/isos/8.0/SHA256SUMS.asc

      It's a good habit to check your downloaded ISO against the SHA256 sum and for better security also check the signature of those sums. Although our mirror redirector does try to detect file changes on mirrors, it's shoud always be envisioned that a mirror (or in the worst case our source mirror) gets hacked and managed to provide both fake ISOs and SHA256 sums. But they can't fake the signature.

      Stay up to date

      Run yum update regularly. We'll fix bugs that are detected regularly until the release candidate. Subscribe to this thread (and make sure to activate mail notifications in the forum parameters if you need them): we'll announce every update to the beta here.

      What to test

      Everything! 🙂

      Report or ask anything as replies to this thread.

      A community effort to list things to be tested has been started at https://github.com/xcp-ng/xcp/wiki/Test-XCP

      posted in News
      stormiS
      stormi
    • XCP-ng 8.1 Release Candidate now available!

      Hello to everyone.

      The Release Candidate (RC) release of XCP-ng 8.1 is available right now 🚀 .

      This post is a mostly a copy-paste from the beta release announcement, with additions regarding the RC release.

      Stability status

      Good as far as we call tell from our tests and beta feedback. I would personally use it in production (actually we probably will very soon at Vates). The main unknown is how well the new coalesce algorithm will perform. Now is the time for as large testing as possible before the final release.

      What changed

      Here's what changes from XCP-ng 8.0. Changes since the 8.1 beta are in bold characters.

      Non-exhaustive list:

      • Based on Citrix Hypervisor 8.1 (https://docs.citrix.com/en-us/citrix-hypervisor/whats-new.html).
      • Same base version of CentOS (7.5)
      • Same base version of kernel (4.19, with more patches of course)
        • Latest kernel hotfix from CH 8.1 included in the RC release.
      • Xen 4.13
      • UEFI support for guests is not experimental anymore
      • Support for Secure Boot is NOT INCLUDED because it relies on Proprietary packages. We're raising the issue with the Xen community to see how to provide a FOSS implementation.
      • Citrix announces:
        • "Improved performance for VM imports and exports that use the XVA format" thanks to the use of a very efficient hash algorithm
        • "Storage performance improvements"
        • "New Windows I/O drivers with improved performance"
        • (From https://bugs.xenserver.org/browse/XSO-951) The next update (apparently not published yet as of 2020-01-27) of the Windows Drivers through Windows Update should at last be compatible with non-english locales!
      • chrony replaces ntp
      • Support for PV guests is now deprecated
        • templates for creating PV guests have been removed
        • existing guests will still run
        • it is advised to convert them to HVM guests
        • a compatibility layer should be provided in the future for PV guests that really can't be converted. But really anyone who can convert to HVM, should
        • due to how 32-bit PV guests work, keeping it functioning on newer hardware with newer features comes with an increasing performance cost, and the linux kernel is about to drop support for 32-bit PV guests
      • Support for AMD EPYC 7xx2(P) added
      • Dynamic Memory Control (DMC) is deprecated and will be removed in the future.
      • VSS and quiesced snapshots support is removed, because it never worked correctly and caused more harm than good.
        • For backups, we are working on support for backups that include the guest RAM to replace the need for quiesced snapshots.
        • Note that Windows guest tools version 9 (the default for recent versions of Windows if you install through Windows Update) already removed VSS support, even for older versions of CH / XCP-ng
      • For new local storage repositories using the EXT filesystem, it now defaults to ext4.
        • The transition from our experimental ext4 storage driver is not automatic.
        • Instructions for transitioning written in specific section below.
        • sm-additional-drivers package updated to refuse to create new experimental ext4 SRs since ext4 is already the default with the ext driver.
      • Status of our specific packages:
        • Experimental support for XFS in local storage repository still available through the sm-additional-drivers package.
        • ZFS still available as an additional package and updated to 0.8.3.
        • Alternate kernel now available, version 4.19.102 (probable update to 4.19.108 before final release). Installing it now automatically adds a new boot entry in grub's configuration, to make testing easier. Default entry remains that of the main kernel.
        • netdata RPMs are now ready
          • @r1 contributed a fix to netdata project to bring support for Xen 4.13
          • @stormi made netdata cache be RAM-only to workaround an upstream bug that could make the disk cache grow forever
      • Plans are laid out for simpler installation and maintenance of Windows guest tools. Unfortunately, we haven't found resources yet to implement them so the current state remains that of 8.0. If you're a developer on the Windows platforms, we're hiring! (full time or part time, contracts or hires) - Contact us.
      • Installer improvements in 8.1 RC: see section below.
      • New leaf coalesce logic of VDIs with dynamic limits: see section below.
      • Fixed VM Autostart issues in 8.1 beta when updated from 8.0 through yum (upstream bug https://bugs.xenserver.org/browse/XSO-978)
      • Fixed netxtreme drivers (bnx2x module) that crashed with some models
      • Updated zstd to 1.4.4. Possibly even better perfs according to upstream. Still no import/export comparative benchmarks to 8.0. Does anyone volunteer?

      Installer improvements in 8.1 RC

      Our installer now offers two new installation options. In BIOS mode, access them with F2 when offered the choice. In UEFI mode, see the added boot menu entries.

      • First new option: boot the installer with a 2G RAM limit instead of the 8G default. This is a workaround for installation issues on hardware with Ryzen CPUs. Though those are Desktop-class CPUs and not supported officially in the HCL, we tried to make it easier to workaround the infamous "installer crashes on Ryzen" issue.
      • Second new option: boot the installer with our alternate kernel (kernel-alt). That kernel, built and maintained by @r1 for the team, is based on the main kernel, with all upstream kernel.org patches from the LTS 4.19 branch applied. It should be very stable by construction but it receives less testing. That option is there for cases when the main kernel and drivers have issues, so that you can quickly test if kernel.org patches have fixed it already. It will also install the alternate kernel in addition to the main kernel as a convenience. If kernel-alt fixes issues for you, the most important thing to do is to tell us so that we may fix the main kernel!

      Announcement about our former experimental ext4 SR driver

      It is now deprecated in 8.1. For a good reason: in XCP-ng 8.1 and above, following upstream changes, the ext driver now formats new SRs as EXT4. Existing SRs are untouched (so remain formatted to EXT3).

      There is no easy way to convert an existing SR created with our driver, so those using it will need to move the VDIs out (to another SR or to export them), destroy the SR and create an EXT SR instead. Make sure to do this on XCP-ng 8.1.

      The sm-additional-drivers package remains available in XCP-ng 8.1 in order to ease the transition. However I've broken the sr-create command on purpose. Any attempt to create a SR of type ext4 will result in an error with a message that explains that you need to use the ext type instead.

      Our experimental driver will be completely removed in a later release, possibly XCP-ng 8.2. Unless someone convinces me to delay the removal for a good reason. I will accept reasons such as "I know I shouldn't have used the experimental driver in production, but I did and need more time to convert my SR while at the same time I really need feature xxx from XCP-ng 8.2", but I really would prefer to drop it in 8.2.

      Feedback from people doing the transition is welcome to make sure we document the transition in the best way possible.

      New leaf coalesce logic with dynamic limits

      I have backported patches from sm's master branch, that implement a new, smarter, logic for leaf coalescing.

      Those interested in the patches, see https://github.com/xcp-ng-rpms/sm/commit/ed1a55d727846cf5777c8258e6a8f3b068e8a35b (python code).

      Feedback wanted.

      Documentation

      At this stage you should already be aware that our main documentation is in our wiki and you should also know that you can all take part in completing it. It's improving continuously and still has room for improvement.

      How to upgrade from XCP-ng 8.1 beta

      Just use yum update or Xen Orchestra as if you were installing updates to a stable release.

      How to upgrade from previous releases

      Since XCP-ng 8.1.0 is a minor release, both upgrade methods are supported:

      • From the installation ISO
      • From command line using yum (from XCP-ng 8.0 only!)

      Refer to the upgrade howto: https://github.com/xcp-ng/xcp/wiki/Upgrade-Howto

      Downloads:

      • Standard ISO: http://mirrors.xcp-ng.org/isos/8.1/xcp-ng-8.1.0-RC1.iso
      • Net-install ISO: http://mirrors.xcp-ng.org/isos/8.1/xcp-ng-8.1.0-RC1-netinstall.iso
      • SHA256SUMS: http://mirrors.xcp-ng.org/isos/8.1/SHA256SUMS
      • Signatures of the sums: http://mirrors.xcp-ng.org/isos/8.1/SHA256SUMS.asc

      If your browser tells you that the page is redirected in a way that prevents from loading the page correctly, this is a known issue. Long story short, it's caused by a wrong security header sent by the forum software, which impacts all non HTTPS requests to the xcp-ng.org domain. Try in Private Navigation mode or use curl or wget.

      It's a good habit to check your downloaded ISO against the SHA256 sum and for better security also check the signature of those sums. Although our mirror redirector does try to detect file changes on mirrors, it's should always be envisioned that a mirror (or in the worst case our source mirror) gets hacked and managed to provide both fake ISOs and SHA256 sums. But they can't fake the signature. See https://github.com/xcp-ng/xcp/wiki/How-to-check-the-authenticity-of-files-downloaded-from-XCP-mirrors.

      Stay up to date

      Run yum update regularly. We'll fix bugs that are detected regularly until the final release. Subscribe to this thread (and make sure to activate mail notifications in the forum parameters if you need them): we'll announce every important update to the RC here.

      What to test

      Everything and Anything!

      Report or ask anything as replies to this thread.

      A community effort to list things to be tested has been started at https://github.com/xcp-ng/xcp/wiki/Test-XCP

      Feedback is welcome both about successes and failures.

      0 stormi committed to xcp-ng-rpms/sm
      New leaf coalesce logic with dynamic limits
      
      Patches backported from master
      posted in News
      stormiS
      stormi
    • Great projects have great documentation. Is XCP-ng a great project?

      Hello to everyone.

      There's a very important way to prove to the world that your software is good: excellence in documentation. A project without good documentation is not appealing and looks un-professional.

      I mentioned it here or there, but never made a proper announcement, so here it is: we are now using the wiki on our github project to store documentation:

      https://github.com/xcp-ng/xcp/wiki

      Now, as you can see, it's missing a lot of useful information. Every red link leads to a non-existent page that should exist, and I probably forgot to add many of them. Thankfully, our community comprises many experienced users of XS and XCP-ng, so we should be able to fill the gap.

      I'm myself totally unable of writing documentation about storage or networking. My field of expertise is packaging, updates, releases, patching, writing some code. So I only write about what I know. But I'm sure you're not thinking that I will write the documentation alone.

      So this is the official start of the "let's improve the documentation together" campaign. Any github user has write access to that wiki (it's versioned so we can revert changes from trolls if needed).

      Don't ask for permission before adding or modifying something to the documentation. Just do it, and others will review it.

      Even the structure of the home page can be modified. I made one to help us start and see where contributions are needed, but it's just a way to help us start.

      Who's in? If you were looking for a way to get involved in XCP-ng but did not know how, here's your chance!

      posted in Development
      stormiS
      stormi
    • XCP-ng 8.3 public alpha 🚀

      It's now live! ♥

      https://xcp-ng.org/blog/2022/11/18/xcp-ng-8-3-alpha/

      posted in News
      stormiS
      stormi
    • Status update on XCP-ng 7.5

      Hello everyone.

      I'm Samuel Verschelde. I started working full-time on XCP-ng on the 18th or June, so little more than one week ago. It's a pleasure to join your community and to devote my time to this free software project.

      Obviously, my first mission targets the release of XCP-ng 7.5. So I figured I'd write a status update post to let you know what's been done, what is being done and what remains to be done. It's easy to get carried away by technical work and to forget to communicate, and I'll try not to fall in this trap. Since I'm still quite new to XCP-ng, please forgive me in advance any approximation or mistake in what I'll write. Just don't hesitate to point any mistake I might be doing, or any omission.

      What needs to be done

      So, basically the process of releasing the new version of XCP-ng, at the moment (this will evolve), is as follows:

      • Get the installation and source ISOs from XenServer 7.5.
      • Rebrand to XCP-ng and remove trademarked material (Citrix name, XenServer name, Citrix logo, splash screen...).
      • Modify the licensing system to remove the restrictions for features that depend on free software.
      • Remove proprietary software components from Citrix that we aren't allowed to redistribute.
      • Fix a few known bugs
      • Create an update repository for transitioning from 7.4
      • Build the installation ISO
      • Test (internally at first, but we'll quickly involve the community)
      • Release
      • (ideally, because we're a free software project after all) Provide source RPMs.

      So were are we at this stage?

      Rebrand to XCP-ng and remove trademarked material

      Mostly done.

      We do this for legal reasons, and Citrix obviously doesn't want its name (or XenServer) to be associated with XCP-ng.
      Amusingly, though, they added their name in the description of several packages in 7.5. Some of these additions are clarifications, so that's good to help us detect proprietary software or trademarked material among the free software components.

      But some other are suprising, such as what they did to the linux kernel package: they added a Citrix logo image in the package (which otherwise contains free software), and then changed the package license from GPLv2 to Portions GPL, Portions Non-Redistributable (See description). And description of the package now contains:

      Citrix, the Citrix logo, Xen, XenServer, and certain other marks appearing
      herein are proprietary trademarks of Citrix Systems, Inc., and are
      registered in the U.S. and other countries. You may not redistribute this
      package, nor display or otherwise use any Citrix trademarks or any marks
      that incorporate Citrix trademarks without the express prior written
      authorization of Citrix. Nothing herein shall restrict your rights, if
      any, in the software contained within this package under an applicable
      open source license.

      Portions of this package are © 2017 Citrix Systems, Inc. For other
      copyright and licensing information see the relevant source RPM.

      A lot of claims for an added logo.

      Since the kernel contained by this package is free software, we made a new package without the added claims and without that added logo, so that we can redistribute it.

      Modify the licensing system to remove the restrictions for features that depend on free software

      We hoped we could simply reuse our package from 7.4.1 but it seems it's not sufficient. Investigations by @johnelse are in progress. Maybe they changed the protocol, maybe we just need a rebuild against latest xapi.

      Remove proprietary software components from Citrix that we aren't allowed to redistribute

      Some are easy to remove, such as the ParaVirtualization (PV) tools for Windows, which are proprietary. I've been told that Xen Orchestra has support for installing them easily, so we shouldn't miss them too much.

      There's one that's giving @johnelse trouble, though: EMU Manager

      This closed-source component is tightly coupled to other free software core components. Since I know little about it, I'll let John explain:

      emu-manager is a layer between xenopsd (the host-level domain management daemon) and xenguest (which deals with the creation of xen domains) and vgpu (which does the graphics emulation for vGPU)
      It is invoked when VMs are suspended, resumed or migrated

      To put things in a few words: there's a close-source component that we can't remove without losing suspend, resume and migrate features. So we have to replace it with a free-software component of our own, and that's a hard work: the interfaces are public but not the internals. And we'll lose the vGPU migration ability in the process.

      We expect to finish this in two weeks from now, but that may slip. If you think you can help, contact @johnelse or come discuss on the #xcp-ng-dev IRC channel on freenode (we both are on a European timezone).

      Fix a few known bugs

      • Broken link to XCP-ng center in the HTML welcome page: fixed for 7.5.
      • Missing /etc/shadow and other files in install.img: will be fixed when building the new ISO images.
      • Fix xcp-python-libs bug mentioned at https://xcp-ng.org/forum/topic/79/configure-dom0-memory-not-work
      • Maybe more? I'm not sure this list is exhaustive.

      Create an update repository for transitioning from 7.4

      Nearly done.

      Build the installation ISO, Test, Release

      Depends on the above other tasks.

      Community involvement

      Now that I'm available almost all the time, it should become easier to include contributers from the community. We don't have the target infrastructure for that yet, but it's already possible to help at various stages. So don't hesitate to discuss it on this forum, to contact me ( stormi-xcp@ylix.fr ) or to come to chat on freenode's #xcp-ng-dev IRC channel.

      And if you read all of this, thanks!

      posted in Development
      stormiS
      stormi
    • RE: Alert: Control Domain Memory Usage

      FYI, I have just published security updates today PLUS the fixed ixgbe driver as an official update to XCP-ng 8.1 and 8.2.

      We made it. This is the end of this huge thread.

      A big thank you to everyone involved in debugging the issue.

      And this is not a 🐟 :D.

      posted in Compute
      stormiS
      stormi
    • Drivers for recent homelab NICs in XCP-ng 8.2

      Context: various recent devices on the consumer market require network drivers which are not present in XCP-ng 8.2.

      Based on the work made with @Andrew for XCP-ng 8.3, I've finally found some time to backport the drivers to XCP-ng 8.2.

      The following optional driver packages will soon be updated on the default repositories:

      • igc-module (backported from kernel 5.10.150): adds support for Intel I225/I226.
      • intel-e1000e-alt (updated to 3.8.7): adds support for Intel I219-V.
      • r8125-module (updated to 9.010.01) for RealTek r8125. Quoting @Andrew:

        Note: This 8125 driver has SG/TSO, PTP, RSS enabled by default.
        Note: This 8125 driver has (optional) firmware loading enabled. Please manually download the rtl8125 firmware and install in XCP in /usr/lib/firmware/rtl_nic .
        Note: The 8125 Chipset/PCI-E card/driver has been known to cause system problems and crashes (not an XCP problem).

      These are Additional packages, which means only best effort support is provided for them.

      Update (2023-05-03): packages now moved to the xcp-ng-updates repository, which means they can be installed with a simple yum install name_of_package, without the need for extra parameters.

      posted in Hardware
      stormiS
      stormi
    • RE: XCP-ng 8.3 betas and RCs feedback 🚀

      I'm publishing new updates to the base repository of XCP-ng 8.3:

      • Security fixes for AMD
      • Debian 12 VM template
      • Removal of the old and unused experimental EXT4 SR driver. Don't jump: the main EXT SR driver still uses EXT4. I'm talking of the old experimental driver we added back then when the default EXT driver would use EXT3 only. This experimental driver has been deprecated since XCP-ng 8.1.
      • smartmontools updated to version 7 which brings JSON output
      • A fix for live migration support in IPv6-only pools
      posted in News
      stormiS
      stormi
    • XCP-ng 8.3 betas and RCs feedback 🚀

      XCP-ng 8.3 beta 1 is released!

      Announcement: https://xcp-ng.org/blog/2023/06/22/xcp-ng-8-3-beta-1/

      This thread is the place where we can discuss this release and where all testers can provide feedback.

      Update: AND now Beta 2 released too. We're keeping the same thread.

      posted in News
      stormiS
      stormi
    • RE: XCP-ng 8.2 updates announcements and testing

      Hello here! I hope you are ready, because we'll have a train of update candidates for you to test shortly 🙂

      posted in News
      stormiS
      stormi

    Latest posts made by stormi

    • RE: XCP-ng 8.3 updates announcements and testing

      @gduperrey said in XCP-ng 8.3 updates announcements and testing:

      Since it doesn't indicate that an updated 8.2 is actually 8.2.1, only the major version is displayed.

      Not a very good example actually 😄 (but what's true is that for 8.2 we didn't add a "LTS" mention next to the version number in the system either).

      37210535-b72a-49e3-aeb0-ad59cbbdd82e-image.png

      But yes, we decided not to increment the version number for XCP-ng 8.3.0. That breaks compatibility with some third party software because they wouldn't recognize a "8.3.1".

      However we're working on a secondary version identifier that would allow you to know your precise patch level.

      posted in News
      stormiS
      stormi
    • RE: XCP-ng 8.3 updates announcements and testing

      @gb.123 Yes. If you think it's not clear in the blog post, I'll think how I can word it.

      Current wording:

      This announcement does not represent a new release. It applies to the existing XCP-ng 8.3.

      If you're already running XCP-ng 8.3, you're on the LTS version. There's no need for a full upgrade. Standard package updates will keep your system current.

      posted in News
      stormiS
      stormi
    • RE: XCP-ng 8.2 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.

      • openssh: Fix low priority CVE-2025-26465 DoS attack when VerifyHostKeyDNS is "yes" or "ask" (The Default value has not changed: "no")
      • samba: Fix vulnerabilities which are very unlikely to be exploitable on XCP-ng but are reported by security scanners.
      • xcp-ng-release: This update adds a certificate to resolve a TLS handshake error, particularly when deploying XOA from CLI using curl.

      Test on XCP-ng 8.2

      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.

      No specific steps for these updates for XOSTOR users.

      Versions

      • openssh: 7.4p1-23.3.2.xcpng8.2
      • samba: 4.10.16-25.el7_9
      • xcp-ng-release: 8.2.1-16

      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
      stormiS
      stormi
    • RE: XCP-ng 8.3 updates announcements and testing

      You probably saw it, but just in case: https://xcp-ng.org/blog/2025/06/16/xcp-ng-8-3-is-now-lts/

      Today marks several important updates for XCP-ng 8.3. In a nutshell:

      • It officially becomes a Long-Term Support (LTS) release, as previously announced when it was first released on October 7th, 2024.
      • We are releasing updated installation images ("ISOs") that include installer improvements and all updates published since the original release.
      • XOSTOR, our hyperconverged storage solution powered by LINSTOR, is now officially supported on XCP-ng 8.3.
      • A new, dedicated upgrade ISO is available to support upgrading from an 8.2 pool that includes a XOSTOR storage repository.
      posted in News
      stormiS
      stormi
    • RE: XCP-ng 8.3 updates announcements and testing

      The above issue is solved in packages that we haven't released as an update yet, that @Andrew tested.

      posted in News
      stormiS
      stormi
    • RE: VM migration failure

      We do advise to jump to 8.2 from earlier releases, before jumping to 8.3.

      posted in Management
      stormiS
      stormi
    • RE: XCP-ng 8.3 updates announcements and testing

      @Andrew Does restarting the toolstack bring the stats back?

      CC @Team-XAPI-Network

      Regarding coretemp, @r1's module doesn't work anymore with Xen 4.17. See https://github.com/xcp-ng/xcp/issues/669. A possible workaround is using IPMI readings, when available. For a better solution, there's work needed in Xen.

      (CC @Team-Hypervisor-Kernel, FYI)

      mikhail-shevtsov-wiregate created this issue in xcp-ng/xcp

      open XCP 8.3 coretemp module doesn't detect any sensors #669

      posted in News
      stormiS
      stormi
    • RE: XCP-ng 8.3 updates announcements and testing

      said in XCP-ng 8.3 updates announcements and testing:

      here are the pre-release ISO images for a refreshed XCP-ng 8.3 installer

      Last call 🙂

      posted in News
      stormiS
      stormi
    • RE: XCP-ng 8.3 updates announcements and testing

      A few days late because internal tests led to a few fixes, here are the pre-release ISO images for a refreshed XCP-ng 8.3 installer:

      https://repo.vates.tech/tmp/

      $ cat SHA256SUMS
      22deae59e7c5cff7d4691c447af9dbf27b29a372748c1844c280bdc212ef2a5f  xcp-ng-8.3-20250606-linstor-upgradeonly.pre3.iso
      9a5dcc8d98949ee207d28307b8b94320d1ffd24841e34ca74e1c0f0422e5ecab  xcp-ng-8.3-20250606-netinstall.pre3.iso
      4d6f5a99da0d70920bc313470ad2b14decab66038f0863ca68a2b81126ee2977  xcp-ng-8.3-20250606.pre3.iso
      
      1. No need to upgrade XCP-ng 8.3 with these. It is not a new release. It's refreshed installation images, with all updates included.
      2. When we release them, at the same time, XCP-ng 8.3 will be officially labeled LTS. Again, the existing XCP-ng 8.3 that you already use. Not a new XCP-ng release.
      3. This is also when XOSTOR becomes officially supported in XCP-ng 8.3 🎉.
      4. 8.2 to 8.3 upgrade with XOSTOR required a specific treatment, to get a compatible LINSTOR version installed on upgrade. This constraint we had to handle was caused by Linstor not supporting rolling upgrade. For this, we provide a dedicated upgrade ISO (-linstor-upgradeonly). After the upgrade, if there are available updates in 8.3 for linstor, then you can follow the usual update process (which also contains specific steps for XOSTOR such as updating linstor-satellite first on all hosts and restarting the services on all of them, still due to linstor not supporting rolling update. That's something that XOA's RPU handles automatically since a few releases, by the way).
      5. Some packages are slightly newer in the ISOs than in 8.3's update repositories. The only reason is because I didn't want to push updates so soon right after the previous batch, so that XOA doesn't tell you that you are outdated and need to update. But of course these updates will also come to existing XCP-ng 8.3 hosts soon. They're not just for the ISOs.
      6. The netinstall ISO image will pull the original 8.3.0 packages at the moment, so if you want to use it you first need to create a netinstall reposistory somewhere by extracting the full installation ISO, and point at it.

      Regarding testing we are interested on all kind of feedback. Installations, upgrades with and without XOSTOR, and everything you want to test that seems pertinent to ensure there are no regressions when compared to the original 8.3.0 installation ISOs.

      posted in News
      stormiS
      stormi
    • RE: XSA-468: multiple Windows PV driver vulnerabilities - update now!

      said in XSA-468: multiple Windows PV driver vulnerabilities - update now!:

      @Tristis-Oris

      1. We do plan a way to remove the warning for VMs that you would choose.

      That's now done and will be included in the next update to the latest update channel for XOA. VMs with the HIDE_XSA468 tag will not be included in the vulnerability detection.

      posted in News
      stormiS
      stormi