@olivierlambert I will try to... Perhaps, it is related to the untrusted certificate of my installation.

This requires some extra plugins to be able to do it, and as it's rather "advanced"/not usual for the main XCP-ng use cases (which is connecting to iSCSI/NFS/shared storages, it's not a priority. Which doesn't mean it's not a good idea or interesting, but there's some work to do it and then to maintain it.

@manilx Just out about this [image: 1728034849236-screenshot-2024-10-04-at-10.39.51.png] Stupid me.... Could have used that a few times, between our production and backup pools which are different. There's always something "new"

@olivierlambert There is only "Dashboard/Alarms" and that is empty for me

@McHenry said in Understanding remote management using XO: @Danp I am using CE so I do not think XO proxy is available at this time. You can setup a proxy yourself using the CE version, just like with everything with the CE version, your milage may vary.

@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

It's 2 different things. It's not because you add RAM that you might need to raise the Node memory either. First, add memory and see if it's enough