@sir_alex_leo
I don't know but are they of the same type ??

   Total Width: 128 bits
    Data Width: 64 bits

   Total Width: 64 bits
    Data Width: 64 bits

@gduperrey
Ran updates on my old hosts
i7 gen4 and ryzen5
nothing exploded yet after ~10h of "testing"

@stormi
Did some minor testing and it seems to work fine

@MathieuRA
Yes, I can confirm if I disable the Secure boot option the VM will start.
After a quick flash of the pxe boot screen, the Debian installer will appear, and I can continue the installation.

The new template for debian 13 is working in XO-Lite

@ThierryEscande
Ran some tests for 20 min
Seems to work fine

[18:39 x1 ~]# ethtool -i eth0
driver: e1000e
version: 5.10.179
firmware-version: 0.13-3
expansion-rom-version: 
bus-info: 0000:00:19.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

@stormi
I ran the xcp-ng-testing and now the migration seems to work

@andriy.sultanov
Sorry, if I only could read...
Anyhow, My updated host running on intel seems to work just fine.

Seems to work fine on my old test rig i7-4710MQ with NFS

@gduperrey

I updated my test host and all seems to work fine.
But I have 1 question:
Do I need to disable the testing repo or is it removed at the reboot?

yum clean metadata --enablerepo=xcp-ng-testing
yum update --enablerepo=xcp-ng-testing
reboot

[10:33 x1 ~]# yum repolist 
Inlästa insticksmoduler: fastestmirror
Loading mirror speeds from cached hostfile
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-base: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-updates: mirrors.xcp-ng.org
förråds-id                                 förrådsnamn                                           status
xcp-ng-base                                XCP-ng Base Repository                                4 376
xcp-ng-updates                             XCP-ng Updates Repository                               125
repolist: 4 501

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

@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

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

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

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

but it still works on 76abf from dec 09

Crap
File restore doesn't work on free version, sorry

@Pilow
I'l spin up my XOA's and test

@Pilow

granular file restore

I'm not sure what granular file restore means but when I read Your first post, I had to test backup/file-restore and I was able to restore files.
XO CE 1640a of dec 03 if I remember correctly

In thin provisioning It would be nice to have info about a VMs actual use of disk space
#Disk Space
46 (73) GB