Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    rzrR
    New security update candidates for XCP-ng 8.3 LTS (kernel) This release batch contains security fix on kernel, version update, some bug fixes and a few improvements. What changed Virtualization & System kernel: Fix Vulnerability: CVE-2026-46243 Fixed the CIFSwitch security vulnerability that could allow privilege escalation from a user with low privileges. intel-microcode: Fix a hang on boot on some platforms (Revert Granite Rapids AP/SP ucode back to IPU 2026.1) Drivers intel-ice: Update to 2.4.5 Adds support for E825-C and E830. Adds support for Link Aggregation (LAG). Various stability, performance, and bug-fix updates. Versions: intel-ice: 1.15.5-2.xcpng8.3 -> 2.4.5-8.1.1.xcpng8.3 intel-microcode: 20260416-1.xcpng8.3 -> 20260416-2.xcpng8.3 kernel: 4.19.19-8.0.46.5.xcpng8.3 -> 4.19.19-8.0.46.6.xcpng8.3 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. What to test As usual, normal use and anything else you want to test. Test window before official release of the updates ~3 days We would like to thank users who reported feedback since our last call for testing: @Andrew, @acebmxer, @flakpyro, @jeffberntsen, @majorp93, @marcoi, @ph7, @pilow, @probain.
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    dthenotD
    @bvitnik Hello, sm-config:vdi_type is the pre-existing one so we are still writing it for compatibility reasons. But you might notice that vdi_type is only written for LVM-based SRs. While image-format is always written in XCP-ng with the QCOW2 feature. So it might be safe to just look at image-format if it exist and if it's not, it's likely a VHD. On LVMSR, you can fallback on vdi_type (and it should work for XS too). Indeed, ISO SRs do not advertise a VDI format. Technically, ISOs could be considered to be raw. It should also be noted that our implementation of QCOW2 is very different from GFS2 QCOW2 of XenServer. Our implementation uses the existing SR types to allow VHD and QCOW2 to co-exist.
  • 3k Topics
    28k Posts
    julienXOvatesJ
    @ph7 said: Xen Orchestra, commit 71fa8 With a snapshot attached to a VM, it is reported to use 0% of 100GB [image: 1764512657473-7fecc14f-bea7-4acb-b5eb-9e2f3c0ac8e6-image.png] And if I remove the snaphot [image: 1764512774124-e25ffd4b-796a-47a5-ae21-c2252d2ffc96-image.png] And that seems to be more accurate Hi @ph7, The VDI storage used space with snapshots has been fixed in XO 6.5 !
  • Our hyperconverged storage solution

    47 Topics
    750 Posts
    olivierlambertO
    Please disable HA and report if you still have the issue.
  • 35 Topics
    113 Posts
    olivierlambertO
    Ah excellente nouvelle Je passe le sujet en résolu !