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

[DustinB]

Another suggestion, collapse non-running VMs into a single group, rather than having them listed individually.

https://feedback.vates.tech/posts/50/collapse-non-running-vms-into-group

[john.c]

@DustinB said:

@john.c This is already viewable under each hosts in the pool.

Then in that case the pools based view restructure can go ahead. Was just concerned about ensuring that it’s still possible to access individual hosts.

[jr-m4]

Small discrepancy: VDIS or VDIs? Which one is it?

Red points out where it's called VDIS.
Green where it is called VDIs.

And as a bonus feedback/question. Why is it called "A VDIS" ?(marked with yellow)

[Patrick]

missing the Health Overview dashboard. if you have 10 pools this was very usefull so I will go back to the old view for now.

also restore a VM is missing only the Backup tab is visible.
if I click on the "eye" it still not there will this feature come in the future?

[benapetr]

@olivierlambert said:

Hi @darthkitty8 !

Thanks for the feedback and idea, can you create it at https://feedback.vates.tech and use the "XO 6" tag? Thank you very much!

Another option would be to just mimic XenCenter design to make it more "Xen native" and have Objects view where you have separate tree node for "Hosts" and then "VMs" so you group all hosts and vms together.

[AlexanderK]

is there any manual for xo6?
I am trying to create a backup but i cannot find how to....

[skipthompson81]

@AlexanderK
xo 6 is rolling out features regularly, for many functions, you must continue to use x05. backup is one of those at this time

[ph7]

After the work You put in fixing
https://xcp-ng.org/forum/topic/12040/restore-only-showing-1-vm/18

It seems like VDI-size in VMs VDIS is back to showing size of snapshot instead of size of VM.

[paramazo]

console view is unreadable even if fullscreen was selected. It was much more usable on XO5.

Iam missing a lot of configurations in XO6 which are available on XO5. New interfaces already feel weird, thats normal habbit, but iam very confused with this one.

Can i make /v5 the default interface on this version?

[olivierlambert]

What do you mean by "unreadable"? Can you be more specific?

Also, more is coming to XO 6 progressively, we'll be on par this year. About /v5 by default, we documented it IIRC.

[paramazo]

@olivierlambert I try to show it with some screenshots on same VM with the same screen

This is XO5:

This is XO6:

can you spot the difference? it seems some kind of scaling is happening here... it looks blurred. What do you think?

[olivierlambert]

Let me ping @Team-XO-Frontend

[jr-m4]

Sometimes "# Disk Space" for VMs reports 0 in the central pane. But the assigned space is shown in the details (right) pane.

This is the same under Pool and Host-level. Sometimes it is shown, but after a reload of the page, it resets back to 0.

Marked the examples in red.

[ph7]

I removed 1 host from the pool and the local storage from that host didn't get purged

[ph7]

just found out that it's the same on XO5

[escape222]

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

[olivierlambert]

Thank you for the great feedback @escape222

Likely a bug indeed

[Greg_E]

@escape222

I assume you made it UEFI? I had the same problem with XO-lite about a year ago. If I created it as bios boot it worked as expected.

[escape222]

@Greg_E Yes it is UEFI

[Greg_E]

@escape222

Maybe try again as a BIOS boot VM, but the times for BIOS boot are nearing an end, so many things have climbed on UEFI only these days that a problem like this is going to be hard to ignore.