Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    5k Posts
    rzrR
    rzr said: New security update candidates for XCP-ng 8.3 LTS (kernel) Test window before official release of the updates ~3 days The testing window is extended a bit, expect also a next batch (to be tested later this month). It has been planned to group updates for the convenience of administrators (stay tuned in blog). Meanwhile If you didn't notice yet, an updated xen package landed in testing repo, it addresses some low risk vulnerabilities as reported at: VSA-2026-017 (XSA-491, CVE-2026-42487) VSA-2026-018 (XSA-492, CVE-2026-42489 - CVE-2026-42490), VSA-2026-019 (CVE-2025-10263, XSA-493) VSA-2026-020 (CVE-2026-42488, XSA-494) More to come soon

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    poddingueP
    That leftover NIC is probably a stale PIF that XAPI is still holding, even though the card is physically gone, and the Refresh button re-scans rather than removing it. The docs have proper "remove a physical NIC" steps that end in forgetting the old PIF with xe pif-forget: https://docs.xcp-ng.org/networking/#remove-a-physical-nic. For the GPU side, the PCI passthrough flow (hiding the device from dom0, then assigning it) is here: https://docs.xcp-ng.org/compute#detaching-a-pci-device. If the GPU still won't show up as assignable once the stale PIF is gone, it might be worth a mention to @Team-Hypervisor-Kernel.

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    G
    @poddingue I need to update a few things and then I plan on trying to see if this was fixed for me. I think I only had 2 Windows machines that were a problem, and only on machines that had a larger disk and were basically empty. The counting zeros seemed to lead to a time out. Just haven't had the time to look at much of anything lately.

  • Our hyperconverged storage solution

    47 Topics
    754 Posts
    SuperDuckGuyS
    @poddingue Hi there and thanks for the info. I forgot to update this post. The issue in the end turned out to be something broken on the backend Xen Orchestra licensing for XOSTOR. Support was able to fix it.

  • Non-English speakers

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