I even had a case where my XOA had multiple NICs (and multiple IPs) The IP that it used to access NFS was not the one I expected... the debug mode of the mount nfs CLI did put that into light. is it the case for you ?

@Pilow - so...I powered down the VM and re-attempted the RPU. It seems snapshots is a deterrent for being able to perform a RPU, because I see VMs migrating now so the RPU can run. For specificity - yes, my XCP Hosts are identical (CPU, RAM, etc); there were no affinities set (see screenshot) [image: 1763483116773-cf9b9ae2-5363-4b66-b367-1b0474e54538-image-resized.png] , etc. Thank you for the assist! I think @olivierlambert or his tech writers need to update the RPU requirements area of the docs. Snapshots cannot be present or RPU will fail. Weird why that is

@WorkAccount1000 Prior to myself finding that option in the config file use to run this command that worked as well.. cd /opt/xo/xo-web sudo yarn run turbo run build --filter @xen-orchestra/web

@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.

I think it's planned for XO 6 adding @gregoire in the loop

Hi, I just responded to your ticket with the steps to update XOA to match your new license. Regards, Dan

On the bottom of each documentation page, there's an "Edit this page" link you can use to contribute

@florent Is there anything in the logs he provided that stand out?

@wezke said in Ansible Role - Install XO from source - Now available: @probain Thank you for sharing your ansible role, ill have a look at it It's far, far from perfect. So there might be a few rough edges that I solved manually. But I welcome feedback.