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
    gduperreyG
    To install XCP-ng tools from the ISO, simply use the following command: bash /mnt/Linux/install.sh -d rhel -m 9 Source: https://docs.xcp-ng.org/vms/#-linux-vms Indeed, it's simply the version that isn't detected by the install.sh script, but the tools install correctly. This issue is present on all Red Hat 10 and derivatives. An RPM package fixing this is in the pipe for XCP-ng 8.3, but I don't have a release date yet, even for testing. But it's in progress

  • All Xen Orchestra related questions/reports

    3k Topics
    26k Posts
    M
    @andriy.sultanov I created a small test setup in our lab. I created a WIndows VM with a lot of free disk space (2 virtual disks, 2.5 TB free space in total). Hopefully that way I will be able to replicate the issue with full backup timeout for VMs with a lot of free space that occurred in our production environment. The backup job is currently running. I will report back once it failed and once I had a chance to test if your fix solves the issue.

  • 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
    90 Posts
    olivierlambertO
    Yes, account aren't related