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

[erwi_2026]

@olivierlambert (first post, def won't be last though, break through being shy) Apologies in advance if wrong location. ;(
Heads up: What I observed, PIF status may show "Disconnected" on healthy OVS LACP bonds

Wanted to flag something in case it saves someone a debugging detour — after upgrading from an older XOA build (472 commits behind) (yes I know) to current master, the network view showed our eth2+eth3 bond's PIFs as "Disconnected" pool-wide, including individual PIFs on 2 of 3 hosts in the per-network detail panel.

Gave me a tense scare (client-facing subnet/vlan), so we went to CLI to get ground truth before assuming an outage (though obvious services working fine in that network).

 * ovs-appctl bond/show on all three hosts: lacp_status: negotiated, both members enabled/may_enable: true, active traffic balanced across both interfaces (balance-tcp).
 * ethtool confirms link detected, 10Gb/s full duplex, both physical NICs.
 * XAPI's own PIF object reports currently-attached: true for the bond master.

So the bond itself is fully healthy — this looks like it's specific to how the PIF status is being surfaced in XO 6, not an actual connectivity problem or a stale XAPI record. Sharing in case it's useful data toward the read-only-mode maturity you mentioned in the announcement.

XO commit: 5.208.3 (rebuilt from source today)
All nodes(3) within the last week:
XCP-ng version: 8.3.0 (xapi 26.1.16, network_backend: openvswitch)

[julienXOvates]

@erwi_2026 I'm not expert on the Networking side so I may be wrong.
I believe this is the expected behavior : the slave interfaces will show as disconnected because only the bonds containing these interfaces should be used.
You may see the difference between the PIF status and Physical interface status in XO6 > Host > Network > PIF details (right side panel) for your bond.

[julienXOvates]

@jacob.becker said:

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 @jacob.becker, this is going to be fixed in XO 6.9 (ie. the Disable state for a host).
I share your point of view about hosts & VM icons, we should also change them.
Thanks !

[coolsport00]

@julienxovates - playing around some more in XO6. I have quite a list I want to submit for feature enhancements (needs, really). One you all already have is being able to open a VM Console in another Tab. I attempted to but it keeps spinning & Console never displays:

I'm using Brave browser. Sometimes this particular browser can cause issues loading pages because of its security. But, I also tried Chrome and same behavior. Thoughts?

[acebmxer]

@coolsport00

Same here on XO from sources - commit f93bb

[coolsport00]

@acebmxer Thank you for confirming as well "Ace". And, I am also running XO from Sources, same build (4 commits behind is all)

[john.c]

@coolsport00 said:

@julienxovates - playing around some more in XO6. I have quite a list I want to submit for feature enhancements (needs, really). One you all already have is being able to open a VM Console in another Tab. I attempted to but it keeps spinning & Console never displays:

I'm using Brave browser. Sometimes this particular browser can cause issues loading pages because of its security. But, I also tried Chrome and same behavior. Thoughts?

@acebmxer @coolsport00 Just like Microsoft Edge, Brave and Google Chrome both share the same upstream Chromium codebase. If there is an underlying bug in Chromium itself, it can potentially affect both browsers simultaneously.

However, because this involves the XO6 VM Console spinning indefinitely, it is usually caused by environment configurations or active development bugs. Here are the best steps to troubleshoot:

• Update XO From Sources: If you are running XO from sources, try updating by building from the head of the master branch. XO6 is moving fast, and this console bug may already have a fix waiting for you in the latest commit.

• Self-Signed Certificates: Open a new tab and navigate directly to your XO instance's IP/domain to explicitly "Accept the risk and continue". Chromium browsers often silently block background Console WebSocket connections if the root SSL certificate isn't trusted.

• WebSockets & Proxies: Ensure your reverse proxy, firewall, or ad-blocker isn't dropping or blocking wss:// (Secure WebSocket) connections, which the console relies on to stream the visual data.

[acebmxer]

@john.c

Updated to latest commit did not help as expected... Also tried firefox an with out reverse proxy...

[john.c]

@acebmxer said:

@john.c

Updated to latest commit did not help as expected... Also tried firefox an with out reverse proxy...

If you’re using a script to help with compiling Xen Orchestra From Sources, please check whether there’s been any compilation issues when compiling it (especially ones related to the VM and Host Consoles). If there are any please grab a copy of the logs from the compilation, update the script and try compiling again.

[Greg_E]

@john.c

Updated both of mine yesterday and no issues, Debian 12 for both. One of them is an ancient HP T630, the other a vm as BIOS boot. Here might be the wrinkle, I haven't applied the latest XCP-ng updates, haven't had the time when things are clear enough to handle it.

[acebmxer]

I am also able to reprodduce in XOA... I can open a support ticket and/or open a support tunnel.