Categories

  • All news regarding Xen and XCP-ng ecosystem

    136 Topics
    4k Posts
    stormiS
    @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). [image: 1750243409436-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.
  • Everything related to the virtualization platform

    1k Topics
    13k Posts
    I
    Plus one for Clonezilla here, has worked for me migrating Rocky from various hypervisors to xcp-ng.
  • 3k Topics
    24k Posts
    A
    Hi, Having the same issue, took me a while to figure out that it was a bug as the last backup got interrupted during a power failure and I thought the issues was to do with that! I reverted to a snapshot pre xoa update and it seems to be working now.
  • Our hyperconverged storage solution

    29 Topics
    639 Posts
    olivierlambertO
    Ping @Team-Storage
  • 30 Topics
    85 Posts
    GlitchG
    @Davidj-0 Merci pour le retour, j'utilisais aussi une Debian pour mon test ^^