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

manilx

@Greg_E You've got a point, actually several.

The scripts exist for a reason because the official way is way to complicated. I still use them, having converted to xcpng @home (scripts) and @business 3 yrs ago.

There should be an official script, definitely. So all are on the same page. They have nothing to loose, everything to gain! The more people use it the better and having a simple way to officially install XO would help that.

Regarding XO6, I don't personally like it at all, mainly because I have to hunt around to find stuff, where in XO5 it's already automatic (not talking about missing features which revert us to XO5).
I actually don't like the UI, it is cramped especially on smaller laptop screens... But this is a personal preference.....

Greg_E

@manilx
Everything I've used so far is 1920x1080 or higher resolution... I guess I'll have to use my ClockworkPi uConsole with it's 1280x720 screen and see what I can see, I may hate it on this little device.

As a Windows user, I've gotten used to things moving locations from one update to the next, but I get it, it's going to take some learning.

acebmxer

When creating new vm in XOv6 it does not set the correct number of cpu's....

I set 4 cpu's and after creation there is only 1. Also the ISO image is not mounted after creation.

Danp

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

When creating new vm in XOv6 it does not set the correct number of cpu's....

I set 4 cpu's and after creation there is only 1. Also the ISO image is not mounted after creation.

Confirmed in my lab. I also noticed that I had to explicitly add a network adapter, which is a change from XO5.

acebmxer

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

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

When creating new vm in XOv6 it does not set the correct number of cpu's....

I set 4 cpu's and after creation there is only 1. Also the ISO image is not mounted after creation.

Confirmed in my lab. I also noticed that I had to explicitly add a network adapter, which is a change from XO5.

That also. I forgot to include that about network adapter. VM does boot and appear to work correct after fixing those issues.

Greg_E

[edit] strike all that, I found them in XO5 and removed them. It was the reshuffling of where things are between the new interface.

acebmxer

Themes are not persistent. If I set a theme Nord in dark mode. It will stay if i log out and log back in. But i close the browser and open new and log in back to default.

I am using https://github.com/ronivay/XenOrchestraInstallerUpdater script. Not sure if that has anything do with it. Cant test is XOA as these update not live in XOA yet.

Noticed this with 2 from two pc's one running windows 11 with brave browser and with Ubuntu 25.10 desktop with brave browser.

olivierlambert

Hmm are you sure you are not in private mode? IIRC, theme is stored within a cookie.

acebmxer

@olivierlambert

No private browsing or incognito mode. Also tried with fresh install of fire fox same issue.

MathieuRA

Hi @acebmxer the bug related to the ISO will be fixed soon (probably tomorrow on the master branch).
@gheppy Same for the CPU provisioning bug.

acebmxer

Just install update on XOA for 6.1 and theme option is there now, and still does not stay after closing browser. Test on win 11 pc with google chrome. Lite mode\dark modes does but themes keeps defaulting to default when closing the browser.

Greg_E

@acebmxer

I need to check, I think my from sources is also doing this, light/dark stays but I need to check themes and see. That said I am probably 3 dozen commits behind at this point and probably going to wait until next week to update any of my XO from sources (yes two, one VM and one on bare metal Debian as a backup).

fluxtor

Background: A scheduled backed that is not enabled is used as a place holder/template for remote triggering via XO API the actual VM to be backed up is set during the API call.

Issue: The VM shown in completed backups log in XO6 is the VM from the template and not the VM actually backed up. XO5 shows correctly, XO6 does not (unless I am missing something!)

aesparragon

It looks like the same IP addresses are being displayed for multiple adapters. Each adapter should only show its own assigned IP addresses.

In the old interface every adaptar show his own IPs.

Best regards,

jacob.becker

Hi!
In XO-5 you can see clearly if a host is in maintenace mode" or not. I'm missing a similar thing to the little green/gray dot from XO-5 in the XO6 treeview.
You can see it in the System- Tab under General Information, but only if the host is already selected.

I personally find it difficult to distinct between hosts and VMs in the treeview if a large amount entries are shown. Especially while scrolling.

Greg_E

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

It looks like the same IP addresses are being displayed for multiple adapters. Each adapter should only show its own assigned IP addresses.

I saw that the other day, you should be able to expand the next block to the right to see the individual connection ports. I think this is one of those "need to get accustomed" to the new interface things. But I'd agree that it is more clear in XO5.

XO-Lite does break them down by PIF, but does not currently show the IP address of that host. Seems like we are wanting a mix between XO-Lite and XO6.