Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    A
    @michael.manley Would it be possible to backport the XSA-498 fixes? I've tried updating the SDK as a whole but it resulted in a lot of churn and caused errors elsewhere: https://github.com/xcp-ng/xenadmin/pull/271 The fixes to the SDK have been posted here https://github.com/xapi-project/xen-api/pull/7176 and here: https://xenbits.xen.org/xsa/advisory-498.html

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    Y
    Just FYI, we had some issues with some Debian VMs for instance, with old kernel where the VM would suddenly take 100% CPU and would we completely frozen and unresponsive. It was in fact Debian enabling the suspend, the guest would suspend and trigger a bug in xen PV driver in the guest kernel which would never be able to wake up anymore. Newer kernel don't have this issue and are able to wake up. I'm quoting Debian here but it might very well happen on other distro

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    T
    I have noticed an issue in the Xen Orchestra backup job status logic where if an individual VM backup failed for any reason, and was then retried and completed successfully on retry, it is still reported as a backup failure. This is seen in both the XO backup status for that job but it also sends a backup failure email, which includes the detail that the vm backup had to retry and was successful (but is still reported as an failure). Can anyone on the Vates team confirm if this is a known issue or if there is a fix in the works? Ideally, with any backup job run, if retries are enabled in the job and a VM backup needs to be retried for any reason, and then ends up completing successfully, the final state of the VM backup should be success. The current behavior just has us investigating failures that aren't really failures. [image: 1784216788435-firefox_obmgyueayi.png] [image: 1784216802882-olk_sngou4ov1v.png]

  • Our hyperconverged storage solution

    49 Topics
    767 Posts
    poddingueP
    That it's stayed quiet since you throttled Velero is a good sign, and it lines up with the concurrency theory rather than anything about the specific volumes. Bumping dom0 RAM makes sense too, since linstor-satellite spiking to roughly 8,700 log lines around the panic suggests dom0 was under real pressure right then. If it does come back, a xen-bugtool --yestoall bundle from the host that panicked, plus the Loki window you already have, would give @Team-Storage something concrete to line up against the DRBD side. I'm not sure whether the real fix sits in Velero's pacing or in how LINSTOR handles concurrent create/delete, but the reproduction you've narrowed down is genuinely useful. Fingers crossed it stays boring from here.

  • 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