Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    A
    @rzr Always a reboot after big updates, as instructed/required.
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    A
    @Aleksander You would need a gpu that support SR-IOV. From NVIDIA that means a non consumer gpu. Edit the below is Ai output. GPU SR-IOV support varies significantly by vendor and architecture, with Intel offering the most extensive hardware-based SR-IOV for consumer and data center graphics, while NVIDIA and AMD rely heavily on proprietary drivers or specific enterprise hardware. Intel Graphics support is the most widespread for virtualization, with 12th Gen (Alder Lake), 13th Gen (Raptor Lake), and 14th Gen (Raptor Lake Refresh) Core processors supporting SR-IOV, as do the Intel Data Center GPU Flex Series and Intel Arc Pro B-Series (requires driver version 32.0.101.8306 or newer). Older generations (6th through 10th Gen) primarily support GVT-g (software-based mediation) rather than hardware SR-IOV, while the Intel Core Ultra Series 1 (Meteor Lake) and Series 3 (Panther Lake) do not support SR-IOV. NVIDIA supports SR-IOV primarily through its proprietary vGPU and MIG (Multi-Instance GPU) features on enterprise-grade hardware, including the A100, A40, A30, RTX A-series, and Tesla lines. While open-source drivers like Nouveau exist, NVIDIA's proprietary Mdev driver is the standard method for enabling SR-IOV and mediation, often managed via tools like sriov-manage in environments like Harvester or OpenStack. AMD SR-IOV support is limited to older FirePro and Radeon Pro cards (e.g., W7100, S7150, V520) using the deprecated GIM or MxGPU drivers. Support for modern Navi and RDNA architecture consumer GPUs is currently unclear or non-existent in open-source ecosystems, with AMD reportedly focusing SR-IOV capabilities on exclusive enterprise contracts rather than consumer hardware. Vendor Architecture SR-IOV Support Status Key Hardware / Notes Intel 12th-14th Gen Core Yes (Hardware) Iris Xe, Data Center Flex, Arc Pro B-Series Intel 6th-10th Gen Core No (Software/GVT-g) HD Graphics 5500–630, UHD 620/630 Intel Core Ultra (Series 1/3) No Meteor Lake, Panther Lake NVIDIA Ampere/Hopper/Ada Yes (Proprietary) A100, A40, RTX A6000, Tesla T4 (via vGPU/MIG) NVIDIA Maxwell/Pascal/Turing Yes (Proprietary) Tesla P100, T4, Quadro RTX (via vGPU) AMD Tonga/Vega/Navi Limited/Deprecated FirePro S7150, W7100 (GIM driver); Modern support unclear
  • 3k Topics
    28k Posts
    M
    @tjkreidl The offsite backup runs at 8 pm and takes 6/7 hours, whereas the hourly runs from 7 am to 7 pm and only take a few minutes. [image: 1776031668155-76eca590-f9f4-4f99-8964-23be858c62c0-image.jpeg] The backup job has 19 VMs, suely this is not too many.
  • Our hyperconverged storage solution

    44 Topics
    731 Posts
    olivierlambertO
    Different use cases: Ceph is better with more hosts (at least 6 or 7 minimum) while XOSTOR is better between 3 to 7/8. We might have better Ceph support in the future for large clusters.
  • 34 Topics
    102 Posts
    B
    La remarque a été intégrée dans l'article: https://www.myprivatelab.tech/xcp_lab_v2_ha#perte-master Merci encore pour le retour.