@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

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

@ovicz
Perhaps upgrade bios ???

@Chico008
Use a file manager outside of XO, it will keep the name of the iso

@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

@Forza
I started experimenting with this function in dec -24 and have run it in "production" in my homelab since jan -25
I suggest You keep the Backup retension (52) to 1.
this is my setup

Sequence

Schedules

And this is the result from one of my VMs

As You can see all the backups from jan - apr and most of may are removed

I am waiting to see what will happen when we go into 2026, If I remember correctly,there was some bug at 2024 -> 2025 but hopefully I get my first yearly backup

@lsouai-vates
No worries, I just wanted to report, I'm not using it, just testing

Xen Orchestra, commit 2dd45 from docs
This is similar to the problem from this thread

https://xcp-ng.org/forum/topic/11227/boot-new-vm-to-iso-in-xo-lite?_=1762071345524

When creating a new VM from v6 with Debian Trixie 13 template.
I can't find any where to disable secure boot and the VM won't start

And I also get this:
The topology is "greyed out"

and no default network

In XO-Lite all is fine. Aren't they using the same code?

New job, try pool.rollingUpdate

@McHenry
Use the builtin function, just press Rolling pool update when there is updates available.
Home/Pools/"Ryssen#

The rest is automatic or should I say, magic

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