mid 2026:

• you can't add a ipv6 address via XOA (XOA5) because the gui lacs the field for the v6 gateway-address
• XOA6 lacks feature to configure ips of the host
• the configuration of ipv6 (static) vie the "gui" on the host seems not be implemented yet (or i am missing something critical)
• command line configuration inside dom0 of the host is afaik not supported ?

Some point looks like minor issues. it would be great to "address" pun intendet that as well

+1 from me as well.
We have 2 server-rooms with 2 XCP-hosts each. Host groups would allow to keep certain HA requirements fo a VM fulfilled while not pinning the VM on one host.

@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.

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.

Hi!

ISO-SR over HBA/FC would be very nice, especially when migration form a SAN vmware-System to XCP-NG.

One other thing is altering. Errors like "VM cannot be migrated" or similar should not be silent but should be very visible / even mailed to the admin.
Another thing (could be cosmetical though) in my opinion is that a failed Rolling upgrade remains visible with a half fulled progress bar in the task-view. this is confusing.

I tried to deploy a small test-cluster today. I noticed that despite the setting for a static IP the nameserver entries are deployed after the first update and package-install, which in my case failed. I haven't tested DHCP yet, but if the order of the script is the same (which i assume) the issue most likely is the same.