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
    P
    @pierrebrunet said: Another thing to check is the exact time between your XO and your host. I installed the host with NTP from "static" DHCP (OK according to https://docs.xcp-ng.org/installation/requirements/) not made any manual changes/configs After I did a RTC adjustment in BIOS 3 days ago, the time now is ~1s ahead This is the output from timedatectl [22:04 x2 ~]# timedatectl status Local time: tor 2026-07-16 22:06:45 CEST Universal time: tor 2026-07-16 20:06:45 UTC RTC time: tor 2026-07-16 20:06:42 Time zone: Europe/Stockholm (CEST, +0200) NTP enabled: yes NTP synchronized: no RTC in local TZ: no DST active: yes Last DST change: DST began at sön 2026-03-29 01:59:59 CET sön 2026-03-29 03:00:00 CEST Next DST change: DST ends (the clock jumps one hour backwards) at sön 2026-10-25 02:59:59 CEST sön 2026-10-25 02:00:00 CET NTP synchronized: no I thought that the time would be adjusted automatically at reboot The first NTP sync should allow a bigger step than when it's already synced. @pierrebrunet said: do you make these backup regularly? They run once a day @ 03:04 before the normal backup that starts @ 03:10 and they have all run OK since July 8, the failed one reported 8 days ago ( post ~85 ) Maybe you should resync your clock NTP is enabled but not synced, I don't know the correct way to sync it In xsconsole/ I tried Use DHCP NTP Servers It changed the RTC clock to the same as UTC time but time was still 1s ahead and NTP not synced. I rebooted the host and I got this: [23:36 x2 ~]# timedatectl status Local time: tor 2026-07-16 23:37:17 CEST Universal time: tor 2026-07-16 21:37:17 UTC RTC time: tor 2026-07-16 21:37:16 Time zone: Europe/Stockholm (CEST, +0200) NTP enabled: yes NTP synchronized: no RTC in local TZ: no DST active: yes Last DST change: DST began at sön 2026-03-29 01:59:59 CET sön 2026-03-29 03:00:00 CEST Next DST change: DST ends (the clock jumps one hour backwards) at sön 2026-10-25 02:59:59 CEST sön 2026-10-25 02:00:00 CET NTP still not synced, Local time 2s ahead, RTC 1s ahead, I don't know, If not someone can show me the proper way to manually resync, maybe I should try to reinstall the host

  • 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