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.

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    P
    @julienXOvates Well not in my daefc witch is newer than 6.5.1 [image: 1780671722090-d2391283-67c1-4c60-9fc1-7f90f6f1f7eb-image.jpeg] [image: 1780672030452-b37742ca-add5-4579-b990-28e0dbca8be5-image.jpeg] ph@romy:~$ df -h Filsystem Storlek Använt Ledigt Anv% Monterat på udev 1,9G 0 1,9G 0% /dev tmpfs 392M 916K 391M 1% /run /dev/xvda2 93G 6,3G 82G 8% / tmpfs 2,0G 0 2,0G 0% /dev/shm efivarfs 128K 52K 72K 42% /sys/firmware/efi/efivars tmpfs 5,0M 0 5,0M 0% /run/lock tmpfs 1,0M 0 1,0M 0% /run/credentials/systemd-journald.service tmpfs 2,0G 4,0K 2,0G 1% /tmp /dev/xvda1 975M 8,8M 966M 1% /boot/efi tmpfs 1,0M 0 1,0M 0% /run/credentials/getty@tty1.service tmpfs 1,0M 0 1,0M 0% /run/credentials/serial-getty@hvc0.service tmpfs 392M 68K 392M 1% /run/user/105 tmpfs 392M 68K 392M 1% /run/user/1000 seems more like 8% to me

  • Our hyperconverged storage solution

    47 Topics
    750 Posts
    olivierlambertO
    Please disable HA and report if you still have the issue.

  • Non-English speakers

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