@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

Tested OK on
Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz

I powered on my spare test "server" and ran this update.
All went fine.
After the reboot I started the fully updated XOA (local installed) and ran it for a few minutes.
then I shut it down but it sat for a few minutes so I did a force shut down from xsconsole.
Rebooted the host again and started the XOA, shut it down and it worked fine
Tested one more time and it went OK.

Upgrade to RC2 worked fine so far with netinstall ISO in ventoy on a 8 gen i5 HP laptop. And a "full" ISO on its own USB on a Lenovo Thinkcentre Ryzen 5 2400GE

No stats :o(
but netdata seems to work

@olivierlambert
I have reported a similar issue with the cpu report:
Lots of performance alerts after upgrading XO to commit aa490
https://xcp-ng.org/forum/topic/9658/lots-of-performance-alerts-after-upgrading-xo-to-commit-aa490/14#

@Bastien-Nollet
I have tested it since the 05c6f release and it seems to work fine

Since I'm not used to using git, I was running a few tests on my "test" host.
I had made a change in my "one line commando"
My memory is not in best shape so I forgot the change and ran it in my update.
Now It's sorted out and ran a new update and voila

@olivierlambert
As usual, I'm an Idiot
No need to involve @lsouai-vates

I am checking what went wrong and report back

@olivierlambert
I'l report tomorrow after next backup tonight

@McHenry
To my experience, no. There will always be 31 deltas
After a few month's it can look like this:
MMMddddddddddddddddddddMddddddddddd