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

And snapshot is 2h diff

I'm too triggerhappy
Not everything has changed.
The replication are still 2h off

Should have been 20:10 and 20:40

And in the schedule it still showing the next running in AM/PM not 24h

should have been 20:52

Buy I'm still happy

@olivierlambert @lsouai-vates
Everything now magically showing the right time and def. timezone

@coolsport00 said in Best Way to Live Migrate XO VM:

I guess I can remove my current ones temporarily from my current Pool and XO then add them briefly to the XOA...we'll see.

You can run several xo/xoa, connected to the same pool, at the same time. It can be quite handy some times.
The easiest way to deploy a xoa is from xo-lite

@lsouai-vates
Today I noticed that there is the same in xo5 (commit 25192)
Jobs with disabled jobs but scheduled in a sequence job are shown with Not backed up VMs

By the BCK_Running tag, it is backed up

@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
My old i7 with e1000e is working fine (except the version not shoving)

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

@stormi
If You are asking me, I can run the New update candidates for you to test! on my "production" home lab server if the testing repo still exist

Cold migration doesn't work, but Warm migration does.
No panic, I can wait for the release