Categories

  • All news regarding Xen and XCP-ng ecosystem

    139 Topics
    4k Posts
    P
    Would it be possible to either have direct links to the exe's without them being zipped? Or list the version number of the xen-guest-agent.exe? I'm installing these through Ansible (see code below). And it would be way cleaner if either of those two wishes could be true. - name: Install Xen Guest tools on Windows hosts when: ansible_system == "Win32NT" tags: xcp_ng block: - name: Install Xen Guest Tools when: ansible_virtualization_type == "xen" block: - name: Copy over Latest Xen PV drivers ansible.windows.win_copy: src: "XenTools-x64_{{ xen_guest_agent_version }}.msi" dest: "C:\\Users\\{{ ansible_user }}\\Downloads\\XenDrivers-x64.msi" force: true - name: Install XenDrivers if the version isnt already created ansible.windows.win_package: path: "C:\\Users\\{{ ansible_user }}\\Downloads\\XenDrivers-x64.msi" creates_path: C:\Program Files\XCP-ng\Windows PV Drivers\XenGuestAgent\xen-guest-agent.exe creates_version: "{{ xen_guest_agent_version }}" arguments: - /quiet

  • Everything related to the virtualization platform

    1k Topics
    14k Posts
    olivierlambertO
    @gregoire we must update our doc and put our Rust tools in 1.0/production. Adding @stormi in copy.

  • All Xen Orchestra related questions/reports

    3k Topics
    26k Posts
    ForzaF
    I noticed that for "Mirror full backup", the process copies every backup, and then immediately removes backups older than retention. This seems unnecesary for full backups as there is no relationship between each backup for a VM. [image: 1764448450610-227425cd-efdc-40cf-9222-4df5bf77df06-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

    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/