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

[ph7]

said in ️ XO 6: dedicated thread for all your feedback!:

#Disk Space
46 (73) GB

I saw now that it's implemented under the VM tab, but it would nice to also have it under

[acebmxer]

@ph7
My used space does not add up to actual used space in vm.

[ph7]

@acebmxer
I think that the disk file don't shrink automatically.
You probably had something in there that has been deleted

[acebmxer]

@ph7

So question what happens when i thinks the vm disk is full? When will it clear up? Only thing i can think of was coping 13gb veeam ISO over few times testing things and stuff. but that has been a while now.

[ph7]

@acebmxer
If I remember correctly, if You migrate the VDI to another SR , it will be shrinked.
But I don't know for shure

[Forza]

@acebmxer said in ️ XO 6: dedicated thread for all your feedback!:

@ph7

So question what happens when i thinks the vm disk is full? When will it clear up? Only thing i can think of was coping 13gb veeam ISO over few times testing things and stuff. but that has been a while now.

No, it will not. You can create a new vdi and move the files over manually.

[acebmxer]

@Forza its the only disk for vm the drive for windows. Reinstall windows... NO...

@ph7 VM was already moved to a new SR.

Other windows VM. I Have not looked at my work production environment yet, or linux vms.

[Alexander 0]

With XO from source if I put config.mounts.toml into /etc/xo-server/ I have to provide absolute paths instead of relative ones

In my case

[http.mounts]
'/v6' = '../../@xen-orchestra/web/dist/'
'/' = '../xo-web/dist/'

doesn't work.

But

[http.mounts]
'/v6' = '/opt/xen-orchestra/@xen-orchestra/web/dist/'
'/' = '/opt/xen-orchestra/packages/xo-web/dist/'

work.

[pdonias]

Thanks for all the feedback!

@ph7 said in ️ XO 6: dedicated thread for all your feedback!:

I found another link that isn't completely fixed
https://xcp-ng.org/forum/topic/10613/suspicius-presentation-of-time-in-backup/

Are you in UTC+1? This one might simply be because the VM's name shows the UTC time while, in the tables, we convert dates to your actual timezone.

@acebmxer, @ph7 said in ️ XO 6: dedicated thread for all your feedback!:

In thin provisioning It would be nice to have info about a VMs actual use of disk space

We're actually in the middle of improving how sizes are measured in general: SRs (thin/thick), VDIs, snapshots, chains of VDIs, transfered vs used vs allocated size, etc.

@acebmxer said in ️ XO 6: dedicated thread for all your feedback!:

XOA v5 links not working...

We're still fixing a few things regarding this. It will most likely be fixed very soon

@Alexander-0 said in ️ XO 6: dedicated thread for all your feedback!:

With XO from source if I put config.mounts.toml into /etc/xo-server/ I have to provide absolute paths instead of relative ones

Both should work. Do you start xo-server in any specific way?

[Alexander 0]

@pdonias said in ️ XO 6: dedicated thread for all your feedback!:

Both should work. Do you start xo-server in any specific way?
I'm using yarn start

This is my unit file:

root@xoa:~# cat /lib/systemd/system/xo-server.service
# Systemd service for XO-Server.

[Unit]
Description= XO Server
After=network-online.target

[Service]
WorkingDirectory=/opt/xen-orchestra/packages/xo-server/
#ExecStart=/usr/bin/node ./bin/xo-server
ExecStart=/usr/bin/yarn start
Restart=always
SyslogIdentifier=xo-server

[Install]
WantedBy=multi-user.target

[ph7]

@pdonias

Are you in UTC+1? This one might simply be because the VM's name shows the UTC time while, in the tables, we convert dates to your actual timezone.

Yes, I'm in CET, UTC+1 and 24h
Yes the Cont.Rep. VMs show UTC. During summertime, it was 2h off.
Its just cosmetics, not "urgent", but still in AM/PM

These are also still in AM/PM

• Snapshots
• backup jobs that run the Sequences schedule
• The next run in job-schedule

[ph7]

Commit 035ee in dashboard
I'm not sure if it's a good idea to show a Backup issue every time a Cont.rep. job is run

It would be more or less a static feature for somebody who run Cont rep frequently. and as a consequence won't react when a proper alert should be displayed