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, xen, intel-microcode) This release batch contains security fix on kernel, version updates, some bug fixes. What changed Virtualization & System kernel: Update to 4.19.19-8.0.46.3 Fixes CVE-2026-43284 (used by the DirtyFrag and CopyFail2 exploits) intel-microcode: Update to 20260416-1 Improve Intel support and security INTEL-SA-01420 xen: Update to 4.17.6-8.1 Minor bugfixes for x86 systems, including calibration of various timers and handling of PCI devices when disabling SR-IOV Control plane xapi: Update to 26.1.4 Minor NUMA fixes UI xo-lite: Update to 0.21.0 chore: upgrade dependencies with known security vulnerabilities (#9640) These vulnerabilities are not believed to affect XO Lite itself. They are fixed as defence-in-depth. Changelog Versions: gpumon: 24.1.0-83.2.xcpng8.3 -> 24.1.0-84.1.xcpng8.3 intel-microcode: 20260115-1.xcpng8.3 -> 20260416-1.xcpng8.3 kernel: 4.19.19-8.0.46.2.xcpng8.3 -> 4.19.19-8.0.46.3.xcpng8.3 xapi: 26.1.3-1.10.xcpng8.3 -> 26.1.4-3.1.xcpng8.3 xcp-featured: 1.1.8-6.xcpng8.3 -> 1.2.1-1.xcpng8.3 xen: 4.17.6-6.2.xcpng8.3 -> 4.17.6-8.1.xcpng8.3 xo-lite: 0.20.0-1.xcpng8.3 -> 0.21.0-1.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 ~1 day We would like to thank users who reported feedback since our last call for testing: @Andrew, @FritzGerald, @IgorGlock, @bufanda, @flakpyro, @manilx, @marcoi, @ovicz, @ph7.

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    julienXOvatesJ
    Hi @mdm, Here is the response from a SME 1- XO get the VM metadata through soap api and create the vm /network XO use the nbdkit + nbdkit-vddk package , connecting to each disk XO connect through NBD to nbdkit XO list the allocated blocks XO create the disk XO read the block and import the data into the disk (though a vhd or qcow2 stream depending on the size) 2- though XO. There is a lot of disk transform occuring here 3- not anymore, it was too brittle, especially on when the disk are locked or not. Also it was not scaling too well 4- see 3- + vddk transfer is overwhelmly faster that previous access through http, is compatible with VSAN and don't lock the disks. (+ also see https://xen-orchestra.com/blog/xen-orchestra-5-110/ section "VMware to Vates (V2V)" where we made key improvements)

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    L
    @stormi that's awesome news, thanks for the news. Digging deeper, I found that my ISOs in my NFS ISO SR have the snapshot-of metadata field populated, and pointing to a VDI that is definitely not its parent. In fact, that parent VDI reports that it is a snapshot-of itself! Hope this helps!

  • Our hyperconverged storage solution

    47 Topics
    745 Posts
    J
    @Mathieu-L linstor n l was included in my original post. All nodes were updated to May 2026 Security and Maintenance Updates for XCP-ng 8.3 LTS, all nodes were restarted. May 2026 Updates #2 for XCP-ng 8.3 LTS was released, and a couple days later I installed on all hosts. No host restarted. When xen04 was restarted, that is when this issue happened. I had used systemctl restart linstor-controller here (https://xcp-ng.org/forum/post/105309) to restart the controller.

  • Non-English speakers

    35 Topics
    113 Posts
    olivierlambertO
    Ah excellente nouvelle Je passe le sujet en résolu !