Categories

  • All news regarding Xen and XCP-ng ecosystem

    139 Topics
    4k Posts
    A
    I was thinking more of updating the entire set of the agent and drivers, similar to how XenServer VM Tools for Windows have it implemented. Using a scheduled job, they regularly check whether an update is available, and if so, they carry out the update of both the agent and the drivers themselves.

  • Everything related to the virtualization platform

    1k Topics
    14k Posts
    M
    That would explain things, and also why my latest test using AlmaLinux 10 also failed in the exact same way that Rocky Linux 10 did. I just wish I read this reply 12 hrs ago Think I'll give this stuff a go on v9 of Rocky Linux and AlmaLinux to check things are working, which I imagine will work fine. I've just confirmed the EPEL version running on AlmaLinux 10 at the time of writing this comment is indeed v 10.1 via the command; sudo yum repoinfo epel @dknight-bg What is the best way to keep track of this stuff proactively, i.e. What would I need to look at so that I could have determined what you have commented myself?

  • All Xen Orchestra related questions/reports

    3k Topics
    26k Posts
    P
    @ph7 still in VDI section [image: 1764517173295-85a9d9d1-be27-4eb9-a89b-db8d7f4bb04e-a04f9520-d831-46b8-a021-3db25ff8e903.png] 100%used VDI widget is halfway through 100%

  • 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

    31 Topics
    88 Posts
    D
    @dani You mentioned in another thread that you're from Spain. ¿Me ayudas con la traducción al castellano para XCP-ng y XOA? Apúntate a https://translate.vates.tech/projects/xen-orchestra/xen-orchestra-6/es/