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

julienXOvates

@jr-m4 Thank you for this feedback. We'll try to make it better based on this !

nasheayahu

Afternoon, my session timed out and I do get the normal login page, but when I login I get this UiAlert Message:

Screenshot From 2026-05-28 12-51-11.png

import{B as e,C as t,St as n,U as r,X as i,_ as a,g as o,h as s,m as c,t as l,x as u,xt as d}from"./_plugin-vue_export-helper-DqPMJZfB.js";import{n as f,t as p}from"./VtsIcon-BoVekVkM.js";import{t as m}from"./use-mapper-M_HHKN3j.js";import{t as h}from"./UiButtonIcon-Df9Z1TJo.js";var g={class:`content`},_={class:`alert typo-body-regular-small`},v={key:0},y=l(t({__name:`UiAlert`,props:{accent:{},close:{type:Boolean}},emits:[`close`],setup(t,{emit:l}){let y=l,b=i(),x=m(()=>t.accent,{info:`status:info-circle`,success:`status:success-circle`,warning:`status:warning-circle`,danger:`status:danger-circle`},`info`);return(i,l)=>(e(),a(`div`,{class:n([d(f)({accent:t.accent}),`ui-alert`])},[c(`div`,g,[u(p,{class:`information-icon`,name:d(x),size:`current`},null,8,[`name`]),c(`div`,_,[c(`div`,null,[r(i.$slots,`default`,{},void 0,!0)]),b.description?(e(),a(`div`,v,[r(i.$slots,`description`,{},void 0,!0)])):o(``,!0)]),t.close?(e(),s(h,{key:0,class:`close-button`,icon:`fa:xmark`,accent:`brand`,size:`small`,onClick:l[0]||=e=>y(`close`)})):o(``,!0)])],2))}}),[[`__scopeId`,`data-v-5b9f5cdd`]]);export{y as t};

... and after back-paging, I was able to login normally.

julienXOvates

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

julienXOvates

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

ph7

@julienXOvates
Well not in my daefc witch is newer than 6.5.1

ph@romy:~$ df -h
Filsystem      Storlek Använt Ledigt Anv% Monterat på
udev              1,9G      0   1,9G   0% /dev
tmpfs             392M   916K   391M   1% /run
/dev/xvda2         93G   6,3G    82G   8% /
tmpfs             2,0G      0   2,0G   0% /dev/shm
efivarfs          128K    52K    72K  42% /sys/firmware/efi/efivars
tmpfs             5,0M      0   5,0M   0% /run/lock
tmpfs             1,0M      0   1,0M   0% /run/credentials/systemd-journald.service
tmpfs             2,0G   4,0K   2,0G   1% /tmp
/dev/xvda1        975M   8,8M   966M   1% /boot/efi
tmpfs             1,0M      0   1,0M   0% /run/credentials/getty@tty1.service
tmpfs             1,0M      0   1,0M   0% /run/credentials/serial-getty@hvc0.service
tmpfs             392M    68K   392M   1% /run/user/105
tmpfs             392M    68K   392M   1% /run/user/1000

seems more like 8% to me

ph7

same in my XOA 6.5.1

julienXOvates

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

ph7

@julienXOvates
The faulty ones are on local SR
If I take a manual snapshot on a NFS VM, I see the correct value

Will test a scheduled one

ph7

Local VMs vith scheduled Incremental or full Backup and CR are affected
NFS VMs vith scheduled Incremental or full Backup are affected
NFS VMs with CR not affected

julienXOvates

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

ph7

ph7 said:

Local VMs vith scheduled Incremental Backup and CR are affected
NFS VMs vith scheduled Incremental Backup are affected

Incremental -> Incremental OR full