@pdonias @julien-f yep fixed now, thanks.

@dguy313 Sunday's XO commit 030b3 solves the issue for me.

@julien-f is aware of this problem and we'll find a way to make it more obvious

you can't configure vGPU limitation at self-service rule, but user can select vGPU at VM creation based on that rule. So it would be unlimited. But i can't really check it with my nvidia cards. and what is Share this VM?

We can make the message clearer, but we advertised multiple time that adding PCI passthrough UI required XAPI changed only available in 8.3

@julien-f Thank you, that's super helpful and even easier than I thought it would be.

I guess I'll partially answer my own question by pointing out that I can background the commands with & so it should run them all at once anyway. Sorry, still new to bash scripting and my Linux skills are a bit rusty but improving.

@olivierlambert Hi, I really appreciate your time! I'm using a US QWERTY keyboard on a 2-year old MSI laptop running Windows 11. I first noticed this issue a few weeks ago when I first deployed xo-server v5.151.0 / xo-web v5.152.1 built from your sources. A little bit ago I actually tried this in Brave browser and using shift worked perfectly fine. Then I tried it in vanilla FireFox and it worked fine there too... I daily drive LibreWolf, a security/privacy version of FireFox and I usually don't ever have issues with it but I'm gonna chalk this keyboard thing up to something related to that. Sorry about that!

The task is green, meaning it's done

@olivierlambert @stormi is the one who helped me find and fix the issue. I just wanted to update my old thread in case someone else happened across the problem until it gets fixed in XO.

Yay! You should try XO 6 UI on mobile, maybe it will be better

@Tristis-Oris That's a "known issue": https://xcp-ng.org/forum/topic/7827/xoa-does-not-refresh-quickly-status-of-nics XCP-ng-center is showing the update.

@Danp Thank you i did it'a was disk issue and i see the documentation that's help

This is an issue inside your guest, so take time to read the logs and try to make sense of it. It's possible you don't have enough resources in the VM to make the migration, but from "outside" it's hard to tell.

That machine has suffered a repeated hardware failure, and has been taken offline, and I think I'll reinstall XCP-ng from scratch on it, so the exact problem described here is moot. However, I'm still interested to learn by what mechanism XOA connects to the VM's VNC console, if anybody feels like teaching me? Thanks in advance.

Do read the specific section in docs about virtualizing xcp-ng. https://docs.xcp-ng.org/guides/xcpng-in-a-vm/

@paco said in Storage IOPS and throughput dropouts?: @nikade Short answer is that the spikes seem to have smoothed out. I'm not really sure what happened. I don't have them at any resolution now. Perhaps some kind of heisenbug. Happy to hear that

@bpsingh76 You should be able to run "xe vdi-list" on these and see if they are attached to anything. If not, it would appear they are just leftover templates.