Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    rzrR
    @MajorP93 said: @rzr Since the targeted test window is over by now, I wonder: what are your plans regarding this set of patches? Will it be released soon? yes this is the plan, we're a bit slower this time because the iso publication is a longer process, but afaik no issue are spotted so far, thank you for your patience.

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    J
    @TeddyAstie From what I've tried...It won't work at all in Linux. It kind of works in Windows, and while I do see some load on the GPU when running something, there's as much if not more load on the CPU. It's not what I expected at least. I've never really gamed on PC, and definitely never Linux. My only uses for GPU's have been in media composition which was always on dedicated systems and Nvidia GPUs. More recently I've been doing some AI tasks, again with passed-through NVidia GPUs. Side tangent... I ran into another workload last night where the app wanted OpenGL...But OpenGL doesn't work with the "normal" VGA adapter in XCP-ng, and I don't have a GPU on that particular pool to try a pass-through. That lead me to VirGL, but it doesn't look like that's gone anywhere.

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    P
    @pierrebrunet Hi! I'll send you xo logs of the errors. In the meantime, I've deleted "Long-term retention of backups" settings and I no longer get duplicated VMs on the DR pool. [image: 1784562046612-cb037ec5-7ad7-4c3f-8a76-1b5be06574f7-image.jpeg] So it seems that this setting is also being used for replication and I cannot use it. Don't have the space for it on my storage, with thick snapshots on lvmoiscsi.

  • Our hyperconverged storage solution

    49 Topics
    772 Posts
    J
    My first idea is to have velero use a different storage class. Something like apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: linstor-ephemeral-retain parameters: linstor.csi.linbit.com/allowRemoteVolumeAccess: "true" linstor.csi.linbit.com/disklessOnRemaining: "true" linstor.csi.linbit.com/disklessStoragePool: DfltDisklessStorPool linstor.csi.linbit.com/placementCount: "3" provisioner: linstor.csi.linbit.com **reclaimPolicy: Retain** volumeBindingMode: WaitForFirstConsumer Then have a cronjob collected the Released pvcs every hour. The problem is that can not work, as velero uses the storage class of the backed up storage class. So I would have to change everything to Retain, and would effectively disable the automatic garbage collection for the cluster. Which might be fine, but would love to avoid it. My second idea is to eliminate the need for the resizing (another work around to hopefully get away from this race condition/bug) I am also not seeing any way to modify the storageclass to round up or pad the pv. This would be to attempt to eliminate the need for drbd_bm_resize. Currently looking into Kyverno Mutating Webhook to dynamically pad these volumes on the fly to see if that would help me out at all.

  • Non-English speakers

    36 Topics
    117 Posts
    B
    Merci beaucoup pour vos retours ! @nathanael-h : C'est l'étape suivante !!! J'ai découvert cluster API le mois dernier et j'ai déja testé sur d'autres plateforme ! ça déchire !!! Je ne savais pas qu'il y avait un support de XCP-ng ! Je finis ma série d'article pour une installation classique et je bascule sur cluster API ! @ataxyanetwork Merci pour ton repo. Je vais regarder ça