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
  • 3k Topics
    29k Posts
    B
    Hello all, I was looking at the code for the perf-alert plugin because I wasn't sure if it followed the same workflow as the backup-reports plugin where it sends emails and delivers to multiple transports. As it turns out, it only sends emails that are configured in the plugin, but I would love it to use the other transports available if they're set up like transport-slack, etc. As a user who is interested in expanding my monitoring footprint in my infrastructure, I think the perf-alert plugin should follow the same reporting/alerting mechanisms as the backup-report plugin and notify to transport-slack along with others. In my case I use Discord, but Mattermost, etc. users would all benefit based on the format the transport-slack plugin already provides. Reading the code it seems like the Plugin system would benefit from having a singular "alerting" layer that you send messages to within each plugin and then the transport plugins just relay the messages to their appropriate APIs (this would likely require rethinking the plugin archictecture however, so not an actionable item), similar to a job queue. I would probably be able to file a PR to add this functionality, but I'm not confident enough to give it a go at the moment as I'd like to understand the implications of adding said code first. For now, I'll leave this as a feature request as I think most people would find this a welcome addition.
  • 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.
  • 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