Categories

  • All news regarding Xen and XCP-ng ecosystem

    142 Topics
    4k Posts
    rzrR
    Thank you every visitors and for those who did not had the chance to visit fosdem check this report: https://xcp-ng.org/blog/2026/02/19/fosdem-2026-follow-up/ [image: vates-xcp-ng-at-fosdem-2026-1.webp] One question, I promised to forward to the forum, how many VM are you running on XCP-ng ? Dozen, hundreds, thousands or more ?

  • Everything related to the virtualization platform

    1k Topics
    14k Posts
    olivierlambertO
    The thing is that it works very well and doesn't need fixes… I know, not usual right? It was so stable that we left it like that waiting for people coming for bugs and nothing happened… We'll cut a 1.0 in the next weeks/months.

  • All Xen Orchestra related questions/reports

    3k Topics
    27k Posts
    V
    Re: XO SocketError: other side closed Hello I'm also experiencing the same issue on my XCP-ng / XOA . My XCP-ng host time to time disappear from XOA. Here is the error I have in journalctl 60.1 Feb 26 21:29:34 xoa xo-server[1628]: '00000000000008673337,00000000000008098348', Feb 26 21:29:34 xoa xo-server[1628]: [Array], Feb 26 21:29:34 xoa xo-server[1628]: '* session id *', Feb 26 21:29:34 xoa xo-server[1628]: params: [ Feb 26 21:29:34 xoa xo-server[1628]: method: 'event.from', Feb 26 21:29:34 xoa xo-server[1628]: duration: 4, Feb 26 21:29:34 xoa xo-server[1628]: call: { Feb 26 21:29:34 xoa xo-server[1628]: }, Feb 26 21:29:34 xoa xo-server[1628]: bytesRead: 976370 Feb 26 21:29:34 xoa xo-server[1628]: bytesWritten: 40192, Feb 26 21:29:34 xoa xo-server[1628]: timeout: undefined, Feb 26 21:29:34 xoa xo-server[1628]: remoteFamily: 'IPv4', Feb 26 21:29:34 xoa xo-server[1628]: remotePort: 443, Feb 26 21:29:34 xoa xo-server[1628]: remoteAddress: '192.168.0.2', Feb 26 21:29:34 xoa xo-server[1628]: localPort: 44468, Feb 26 21:29:34 xoa xo-server[1628]: localAddress: '192.168.0.7', Feb 26 21:29:34 xoa xo-server[1628]: socket: { Feb 26 21:29:34 xoa xo-server[1628]: code: 'UND_ERR_SOCKET', Feb 26 21:29:34 xoa xo-server[1628]: at processTicksAndRejections (node:internal/process/task_queues:82:21) { Feb 26 21:29:34 xoa xo-server[1628]: at endReadableNT (node:internal/streams/readable:1698:12) Feb 26 21:29:34 xoa xo-server[1628]: at TLSSocket.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17) Feb 26 21:29:34 xoa xo-server[1628]: at TLSSocket.emit (node:events:530:35) Feb 26 21:29:34 xoa xo-server[1628]: at TLSSocket.<anonymous> (/usr/local/lib/node_modules/xo-server/node_modules/undici/lib/dispatcher/client-h1.js:701:24) Feb 26 21:29:34 xoa xo-server[1628]: _watchEvents SocketError: other side closed Feb 26 21:28:46 xoa xo-server[1628]: } Feb 26 21:28:46 xoa xo-server[1628]: } Feb 26 21:28:46 xoa xo-server[1628]: ] Here is the node version: node -v v20.18.3 When I looked for XOA version, found it difficult to find it. So I had in fact to go back to XO lite to find that I'm on 2025.11. As for XCP-ng i'm on 8.3.0 . My XOA is hosted on top of XCP-ng on the same machine. Any advice to understand the cause of this issue are welcome. Best.

  • Our hyperconverged storage solution

    41 Topics
    717 Posts
    DanpD
    @tmnguyen You can open a support ticket and request that we reactivate your XOSTOR trial licenses to match your existing XOA trial.

  • Non-English speakers

    32 Topics
    94 Posts
    olivierlambertO
    Difficile de parler de « réalité » avec les benchmarks. Vérifiez aussi l'iodepth (qui dépend du type matériel que vous avez, sur du flash/NVMe vous pouvez monter à 128 ou 256), la latence entre en compte aussi bien sûr. Le bottleneck principal est le monothreading de tapdisk, si vous testez sur plusieurs VMs différentes la somme va monter de manière assez régulière.