Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    I
    Hello, I deleted the entire XOA and downloaded fresh image, recreated configuration and blank SR. The issue is gone. I will test some VDI migrations this week. There are is some performance impact and timeouts when creating 100-200 VMs on single 10 TB SR. I use xo-cli vm.create script. See you later

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    nathanael-hN
    @lknite Hello, sorry if replying in this old thread looks odd... but I wanted to share that we are starting to work on supporting Cluster API. We have an internal proof of concept: /home/nathanael/Images/Captures d’écran/Capture d’écran du 2026-05-05 17-12-22.png[image: 1777999357100-a9596fde-e251-4996-8fc9-3f8e208f9f01-image.jpeg]

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    D
    This seems to be specific to XenServer guest agents?

  • Our hyperconverged storage solution

    45 Topics
    732 Posts
    DAYELAD
    Hello, I’m experiencing an issue on an XCP-ng cluster using XOSTOR. Environment: 3-node XCP-ng cluster XOSTOR distributed storage (2x2Tob nvme on each host) XOA for management Management network 1Gb/s Storage Network 10Gb/s MTU 1500 everywhere (no jumbo frames) So during VM migrations, creation, destroy XOA loses connection to my host pool, VMs keep running normally Hosts remain reachable (SSH / HTTPS / ping OK), Connection comes back after some time 30s to 1min. Observations: No significant CPU or RAM saturation No obvious disk latency issues (iostat looks normal) No errors reported on NICs xapi process remains active (no crash or freeze) The problem is intermittent and seems random. i've monitored nic with iftop and i see no bandwith bottleneck et and can see that XOSTOR is using 10gb network only. Has anyone experienced similar behavior with XOSTOR? And how to Fix it ? Thanks in advance for your help.

  • Non-English speakers

    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.