🛰️ XO 6: dedicated thread for all your feedback!

[olivierlambert]

That's also because XO Lite is replacing basically "nothing before", while XO 5 is 10y full of features that we can't all re-implement at once in XO 6

[Tristis Oris]

Tasks still show completed actions, a month ago events.

No way to install updates. New ui less informative than the old one - no packages changelog.

It also take a time to get into new navigation. Instead of static categories at sidebar, now i can't open Backup while inside pool settings. Need to do extra clicks.

[olivierlambert]

@tristis-oris

See https://feedback.vates.tech/?tags=xo-6 (updates are planned already)

For the rest, if it's a feedback that's not there and not a bug, feel free to add it

[Mathieu]

Has anyone tried to access XO 6 via a reverse proxy?
I'm using nginx proxy manager in a docker container to access my XO instance.
Everything is working fine with XO5 (both XOCE and XOA).
But when trying to access XO6 through the reverse proxy, it shows only a few info, with a circle loading on the top and nothing on the left bar:

If I access XOCE and XOA v6 by their IP address, it's working as expected.

Websocket support and cache is activated on the reverse proxy, nothing else fancy on that side.

Thanks.

[probain]

@Mathieu said in ️ XO 6: dedicated thread for all your feedback!:

Has anyone tried to access XO 6 via a reverse proxy?
I'm using nginx proxy manager in a docker container to access my XO instance.
Everything is working fine with XO5 (both XOCE and XOA).
But when trying to access XO6 through the reverse proxy, it shows only a few info, with a circle loading on the top and nothing on the left bar:

If I access XOCE and XOA v6 by their IP address, it's working as expected.

Websocket support and cache is activated on the reverse proxy, nothing else fancy on that side.

Thanks.

I haven't tried ngnix. But I access my though haproxy:443 - > xo:8443. And that works just fine. But there needed to be a couple of fixes upstream in master to iron out the quirks with non-443 ports and such.

[acebmxer]

@Mathieu I do use NGINX Proxy Manager and i have no issues accessing XO-CE via the new v6 default or the old v5 with working links.

As @probain has stated there have been quite a few updates pushed to fix most issues. My issues were related to the script i used to install XO-CE. The script creator had to update the script to the recent changes made.

Make sure you are on the latest commit and/or update your script and try again.

[Mathieu]

@acebmxer
I found the culprit:

HTTP/2 support needs to be enabled on the SSL tab of npm for v6 to work fine behind the reverse proxy.

It's now working fine.

[acebmxer]

@Mathieu ok. Yeah I already had that enabled. Glad you got it working.

[probain]

Windows guests Console - Reloads every 5-10s.

When trying to use the console for both my Windows 11 and Server 2025. The console reloads every 5-10s. This makes it borderline unusable. Since it resets the viewport/window scroll placement as well. Also the console seems to loose focus when this happens as well. Leading to have to click the console-section to get it in focus, to receive I am not seeing this behaviour in XO5 at all.

I do not see the same behaviour on Linux (Ubuntu 24.04) guests. But they are cli-only. No X/Wayland

Commit: b89c26459cfd301bb92adf0a98a0b2dbab57e487
node: 24.12.0
Management agent 9.1.100-59 on both VMs

Windows 11 has GPU passthrough & bios
Windows Server 2025 - no GPU passthrough , uses uefi

[acebmxer]

Just updated to latest commit - 8e2d9. Trying to create new VM in xov6 and a few issues to start.

New vm settings

• Ubuntu 24.04 template
• 4 cpu cores
• 6 gb of ram
• Ubuntu iso mounted
• No option to adjust topology for cpu cores.

VM was created with 1 cpu core no iso disk mounted

[Gheppy]

For me it's a bit confusing XO6.
For example, why are the icons so small and in such far corners, like New VM? It's like you want it to be hidden.

Isn't it more intuitive if they're at the top/bottom of this menu or in line with title (***-xen01)?

Another thing is the number of allocated processors. In my opinion it is misleading. It shows the total number of allocated processors even to VMs that are not started.
It is not better to be something like:
8 vCPUs running VMs / 4 vCPUs stopped VMs - total number allocated vCPUs 12/ Total CPUs 8.
And something like 8 - green / 4 -red - 12 orange/ 8 grey

Running VM