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
    acebmxerA
    @vlamincktr Just an fyi there is a cost and licensing behind proxy support.
  • 3k Topics
    28k Posts
    J
    @tsukraw said: Hey guys, Looking for some help at understanding auto power on as the documentation possibly looks to need some refreshing. https://docs.xcp-ng.org/guides/autostart-vm/ From the Xen Orchestra, the guide does not mention the pool level it is only under the CLI that it mentions the pool level. Just looking for some clarification. In order for auto power on to function, we need to enable it on the pool level, and then per VM correct? If you have auto power on enabled at the VM level and the pool level disabled, the VM level is ignored, correct? What is actually triggering the power on? Is it XOA or the host itself? I am assuming the host itself, just looking for clarification if XOA VM was part of the systems that went offline, should we expect to see it auto power back on if it is set to auto power on. What determines the start order for auto power on when you have multiple VMs on a host? Thank you!! Yes, it needs to be enabled at pool level and at VM level. I tried once at only enabling at the VM level and it didn’t auto power on, as it wasn’t enabled at the pool level, it started auto powering on once it’s enabled at both levels. It’s configuring a XAPI value as this occurs at the Xen Level. Xen Orchestra is just making this value visible with a nice UI interface toggle.
  • 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.
  • 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.