@MajorP93 this was found in the troubleshooting section of the documentation when i tried to optimise my xoa/xoproxies deployments https://docs.xen-orchestra.com/troubleshooting#memory

@yannsionneau Uploaded contents of /var/crash together with the output of "xen-bugtool --yestoall". Cheers.

@MajorP93 Hi, In the demo dashboard it is intended yes but these percentages are obtained by dividing the free memory by total memory so changing the dashboard to show GB/GiB should be quite straight forward. I've forgot to add to the initial post that there is a advanced dot md file that describes all the available metrics located in "xen-orchestra/docs/docs". Thanks.

@florent @fcgo the host that was queried (with host_ip/export_raw_vdi) will do the export from the shared SR, and will redirect the query to the host that can see the SR otherwise. So it's up to the XO/other orchestrators if they want to distribute the load here.

@florent And here I was trying to give you the benefit of the doubt ... lol

@olivierlambert Not really. Problem exist.

@psafont @olivierlambert As you previously mentioned february and we reached it as of now - I was wondering: do you have any update on when you plan to push the fix to XCP-ng repositories? Thanks and best regards

@Tristis-Oris yes it is likely you're using a newer kernel, we likely need to rebuild the agent using a newer version of the netlink crate.