@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.

@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.

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

@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.

said in Boot New VM to ISO in XO-Lite?:

@coolsport00
Here is a hint in xo 5 when the newly created vm is running.

To be precise, The non working VM created in XO-Lite is not running, it is when it get stuck while trying to boot.

The Alpine one is added from XOA

@olivierlambert
It is the same pool.

@coolsport00
Here is a hint in xo 5 when the newly created vm is running.

@coolsport00
I created the VM in Lite, then checked in XO5

@olivierlambert
When created with XO-Lite, secure boot is enabled but when created with XO5 secure boot is disabled.

XO-Lite:

XO 5

@olivierlambert

Yes, They where all enabled but the clip was so wide I did cut it off.
The only thing I entered was the iso and changed to 2 cpu

New VM in xo5 with uefi

And starting fine in XO5

@olivierlambert
(Fully updated xcp and xo ce 4dfd4)
Default bootorder in 5 and Lite:

Created by XO-Lite:

(I had to check in XO5, didnt find it in Lite)

Created by XO5: