🛰️ XO 6: dedicated thread for all your feedback!
-
As of commit - a3139
VM creation in v6 number of cpu is set to 1 not what is chosen. I choose 5 cpus and 1 is set after creation. ISO is mounted now and Ram is set correctly with correct network.
Still have issues with themes but did not se any mention of them in latest commits.
-
I ran into backup failure this morning, I think someone else mentioned about it in another post. I went to check if there was a newer version of XO since usually things get fixed quickly. so I updated XO to build 9dbc09011.
Few things
- XO loads up now using interface 6 as default.
- As someone else mentioned, about version is blank in v6.
- When I click on V5 link it brings me back to V5 but its broken for me. Sits there saying loading.
- Havent tried using guide to go back to V5 to see why backup failed. Not sure if V6 has enough to figure out backup issue since i havent used it much.
Update: looks like it failing to get something on v5 url.
Update 2: I had to remove LISTEN_ADDRESS="" from my xo-install.cfg to get version 5 working again
-
@pdonias said in
️ XO 6: dedicated thread for all your feedback!:@jacob.becker We're adding the maintenance icon very soon, thanks for the feedback. Regarding VM vs host in the treeview, do you mean that the icon isn't clear enough? Do you have the same issue with pools?
I don't have that many pools, sorry.
The icon for each host got lost in a wall of VMs if you have lets say >50 VMs per host. AFAIK the tree-view allways starts fully expanded. Since all VM belonging to any host are on the same depth of the tree you can scroll over a host easy.
Another thing are VMs which do not belong to a host - they are shown on the same depth as a host.I personally would color the line for a host, but i know that this not the way most design guidlines agrees with.
-
@acebmxer Thanks for the report, we'll check that! Regarding themes, it will remain non-persistent until we implement the full theme system.
@jacob.becker Thanks for the detailed feedback, we'll see how we can improve that
-
@marcoi Sounds like your issue is related to: https://github.com/vatesfr/xen-orchestra/issues/9500
open v5 interface doesn't work if hostname set #9500
-
yeah that was it, i removed the ip address from cfg file and it working now.
-
XO 6 (Enterprise) VM Interfaces shows incorrect IP address assignment on a given VM for a multi NIC VM.
XOA Version 6.0.3
This shows correctly in XO5 Enterprise (and XOCE) without issue.
The expanded view shows both IP addresses that are assigned to different interfaces, but it doesn't delineate nor show properly which IP address is actually assigned to the VIF. See below.
On VIF1, this nic is assigned to the 172.16.1.199 address.
-
Nice catch! Thanks for reporting
-
Snapshots.
There is no information about them in any dashboard.
There is no way to manage them. -
@Hex Have you looked at https://feedback.vates.tech ?
If there's nothing on what you need there, feel free to add an entry!
