@acomav We will actually propose to change the date and time format in XO6 settings, so you would be able to choose between :

• YYYY-MM-DD
• MM/DD/YYYY
• DD/MM/YYYY
  and 12h or 24h time format.
  Hopefully in one of the next 3 months !
  I hope that will answer your need, otherwise let me know !

@oliv77 said:

Hi,

XOA version:
xo-server 5.193.1
xo-web-premium 5.191.0

We've noticed on our production XOA server that when we put an XCPNG host in a pool into maintenance mode, we reboot it and then it reconnects to its pool but is no longer in maintenance mode.
Is it possible to configure the XCPNG hosts so that they automatically return to maintenance mode after a reboot?

Regards,

Oliv77

Hi @oliv77, XO 6.7 - latest - adds this option in REST API and next month we should have the available action (Disable host and evacuate VM) in XO6 !

@jr-m4 said:

@olivierlambert said:

Ah sorry I read it too quickly. This panel is only there in some occasions, but I see the point of only displaying it when we click on a relevant element. Feedback for you @julienxovates

While on the topic of the tree-view panel.
Have you noticed that the indentation changes if there is a chevron indicating that there are VMs on a host? Making it so that the hosts no longer are alinged vertically

Hi @jr-m4, it took some time but we corrected the identation in 6.7 (latest)

This issue should be fixed in the latest release (to be out today).

Thanks a lot @msupport !
@all-ki could you add this to our IPMI doc to be published ?

Hi @acebmxer, thanks for reporting, we identified this bug internally already, we're going to fix it once root cause is found.

@Greg_E well, UI is not ready yet (while REST API is), above screen is just the base !

@acebmxer said:

Just updated to latest commit - 93909

Glade to see more progress on v6.

Yes, that's one of the next big pieces we're going to add to XO6 UI !

We prioritized Network creation in Xen Orchestra as they are mostly Pool-level objects (supposedly with multiple hosts), but we will rework on XO-Lite soon, so you could perform all basic actions as well from XO-Lite.

@Hex said:

Here is a small usability suggestion. In the Resources dashboard, in Pool view and Host view, positions of CPU and RAM are swapped. I occasionally get a brain freeze when switching between Host and Pool dashboard.

Right, thanks! We'll change this !

@johnnezero
To add one more info on top of Mathieu's post : ACL (XO5 only) and RBAC (in REST API + XO6 soon) are completely separate, so better use RBAC as it gives much more flexibility !
Interesting plugin by the way !!!

@ph7 Thanks for those details, very helpful. We'll have a look.

OK, we'll have another look at it, sorry for this !

@ph7 said:

Xen Orchestra, commit 71fa8
With a snapshot attached to a VM, it is reported to use 0% of 100GB

And if I remove the snaphot

And that seems to be more accurate

Hi @ph7,
The VDI storage used space with snapshots has been fixed in XO 6.5 !

@escape222 said:

Slow booting on Debian 13 VM created from a template

I recently tried cloning a VM from a template (created from a full install of Debian 13). What was noticed was that the system takes forever to boot when the VM is created from XO-6. The issue does not happen in XO-5. The VM seems to hang at the TianoCore boot screen .

What I noticed is that when the VM is cloned with XO-6 the boot order somehow changes to Network boot as the first option

This does not happen (change of boot order) if the VM is cloned from XO-5 and there is no boot delay. The boot process seems to wait for more than 2 minutes before it fails network boot and then proceeds normally to boot from the Hard drive

Thanks

Hi @escape222,
For info boot order issue has been resolved in XO 6.5 !

@henri9813 said:

Hello,

I see also this behavior which is "new" since few weeks.

Previously, when a backup start:

• it stake a snapshot ( if there another one before, it delete it ).
• it upload the snapshot as a backup
• it coalesce the backup on the remote.
• end of the game.

Now, the old snapshots are not deleted anymore which can lead easily to some disk full.

Even with a retention of 1, the problem is present.

I observe this only in Backup job, not DR/CR job.

I just updated my XO to latest version, i will see if the issue is fixed.

Hi @henri9813 ,
Issue should be resolved in 6.5.x, can you confirm on your side ?
Thanks!

Hi @andrew
Can you provide some logs ? also assuming you have this issue in the "latest" branch only ?

@tonyp90 great, thanks !

Hi @tonyp90, can you confirm issue is resolved with the latest version ? (I saw 6a5eb1205 is from Oct 2025!). Thanks!

Hi @tonyp90, strange that this happened on your backup host as it is not supposed to, since we prevent VMs to auto-start when Incremental Replication target host is rebooted (see https://docs.xen-orchestra.com/xo5/incremental_replication).
Which XO version are you running ? Do you have a license so you could open a support ticket ?