Categories

  • All news regarding Xen and XCP-ng ecosystem

    139 Topics
    4k Posts
    M
    @uberiain at this point, when I am uninstall the old XCP-ng center software, and install the new msi, I just realized the xcp-ng keeps the settings file in Roaming folder. (C:\Users\user\AppData\Roaming\XCP-ng) When I deleted it I could re-register the servers.

  • Everything related to the virtualization platform

    1k Topics
    14k Posts
    D
    @florent Didn't see your message until now about only applying the fix to only 1 client. I did do a warm migration on client with ticket #7748053. This completed without issue! I tried a warm migration on client with ticket #7747444 and this failed again. Sounds expected as the patch was not on this one yet. Can you push the patch to client with ticket #7747444. Thanks!

  • All Xen Orchestra related questions/reports

    3k Topics
    26k Posts
    W
    Hello, I had a Delta backup job running daily that was working fine on my original XO from sources installation. Late last week, I had to migrate the XO settings to another server. The job itself runs fine when executed manually but the scheduled job doesn't run at all. The job reports "Enabled" and the schedule also reports "Enabled". You can see my setup below. This morning I tried disabling and then enabling the schedule again just in case that would recreate whatever cron job is out there. Is there a config file somewhere that I can look at to verify it's actually scheduled rather than waiting till tomorrow? Thank you! [image: 1764086608703-09db2953-c0b6-4a70-bfed-eb598c403119-image.png]

  • 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 ^^