@BrantleyHobbs You may want to provide some additional details on your setup, ie: Version of XCP-ng Are the host's fully patched? Current XO version or commit etc Have you checked /var/crash subdirectory on the crashed host to see if kernel crash logs were captured? https://docs.xcp-ng.org/troubleshooting/log-files/

also do you have a reverse proxy/ http proxy in front of xo ? it can block the bigger upload by default

@limezest You're right, we'll fix this. With this typo, the elif branch will always be false and not executed, it's dead code. As it is a less common issue than the first branch of the if, the script will left behind this particular case but will still fix the majority of snapshot_of problems. The script can still be used safely.

@poddingue Good evening. Honestly, I'd be totally fine with your taking over a full copy of everything over to XCP-ng and augmenting it over time as new information becomes available. It'd stand a better change of longevity there than in my hands, and all I'd ask for is acknowledgement for the original work. There's no real need for me to keep a totally separate copy of the materials, which would only lead to confusion as things likely would diverse over time. As mentioned above, there are more forum articles and such out there, and when I have time, I'll see if I can hunt some more of those down, as well. I really appreciate what you folks are doing at XCP-ng and the time and effort you're putting into your products. Above all, the feedback and communication have been better than pretty much anyone else I've ever dealt with in the IT industry. P.S. @johnnezero did a super summarizing job with his "Series Overview & Quick Reference" that includes some of the most useful commands in addition to a synopsis of each of the articles. Very impressive!

Thanks for confirming! This is really helpful

Thanks for the clarification, @dsmteam !

Hmm I think we solved that since a while. Ping @julienxovates

@yannsionneau @thierryescande Thank you very much for the updates! We are scheduling some downtime on the services in the upcoming weeks, then I hope to be able to try out all your suggestions. Our fallback plan is to switch the Broadcom network cards for other Melanox cards. I will be posting the results once we have them!

@poddingue this is something that was hidden with the previous system ( same disk chains, but not shown as snapshot ) @julienxovates are you ok to not check the vm tagged as replication from this chech ?

@poddingue We have few Microsoft Terminal server in our XCP-NG VMs. When remote users run for example Chrome rendering is very slow - Chrome can use GPU, but XEON server processors don't have this future. At the moment we use Nvidia cards with 8GB RAM in pass-true configuration. I am looking for solution how to use just one more powerful GPU and share it with VM on this XCP-NG node. That is what I am looking for and when XCP-NG will have solution (without additional Nvidia license), we will be very happy. I will be happy with Nvidia, AMD or Inter GPU, that will property works in VMs.

The sr.scan-driven SMlog growth angle that gumbo2k surfaced is a real lead; there's some context in the storage-related log files reference, but the docs don't go as far as "here's how to throttle it safely on a pool where the underlying disks should spin down." Soft ping to @Team-Storage and @Team-Hypervisor-Kernel: could one of you weigh in on whether other-config:auto-scan=false on the SR is the supported way to reduce scan pressure, or if there's a better lever? I don't want to send anyone down a path that breaks an SR. Apologies if this has already been answered somewhere I haven't seen.