Categories

  • All news regarding Xen and XCP-ng ecosystem

    139 Topics
    4k Posts
    D
    @dom0 They are built from scratch using these components: Upstream Xen Project PV driver sources, which includes contributions from Citrix, Vates, Invisible Things Lab among others, and where we are one of the maintainers; The Rust guest agent, which is developed by us; The installer, packaging and tooling is completely our own. The main repo is here: https://github.com/xcp-ng/win-pv-drivers

  • Everything related to the virtualization platform

    1k Topics
    14k Posts
    D
    Hi everyone, Did anyone else notice that built in SR "XCP-ng VM Tools" cannot be seen by XCP-ng Center 25.0.4 ? [image: 1764231081221-screenshot-from-2025-11-27-09-03-30.png] Happens on 8.3 and 8.2, did not test below that... XO sees it and can mount it SR is visible, PBD was not disconnected Only way for me to get it to work in combo 8.3 + 25.0.4 was to destroy SR and add it from the scratch...

  • All Xen Orchestra related questions/reports

    3k Topics
    26k Posts
    marcoiM
    what build version of XO will start showing v6 interface? I may have missed the announcement. i am currently on Xen Orchestra, commit f4988 Master, commit f4988 and when i try the menu link [image: 1764264980527-fd60acca-9a19-41d6-aaf8-7fe0ab860666-image.png] I get a new tab with error below [image: 1764265011860-fe450aa6-2cb2-4ad1-a14e-1e940971b444-image.png] anything i am missing? or is the XO build not out yet?

  • Our hyperconverged storage solution

    37 Topics
    690 Posts
    ronan-aR
    @TestForEcho No ETA for now. Even before supporting QCOW2 on LINSTOR, we have several points to robustify (HA performance, potential race conditions, etc.). Regarding other important points: Supporting volumes larger than 2TB has significant impacts on synchronization, RAM usage, coalesce, etc. We need to find a way to cope with these changes. The coalesce algorithm should be changed to no longer depend on the write speed to the SR in order to prevent potential coalesce interruptions; this is even more crucial for LINSTOR. The coalesce behavior is not exactly the same for QCOW2, and we believe that currently this could negatively impact the API impl in the case of LINSTOR. In short: QCOW2 has led to changes that require a long-term investment in several topics before even considering supporting this format on XOSTOR.

  • Non-English speakers

    30 Topics
    85 Posts
    GlitchG
    @Davidj-0 Merci pour le retour, j'utilisais aussi une Debian pour mon test ^^