@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

@rzr said:
xo-lite: 0.18.0-1.xcpng8.3

Well I was and still is on v0.19.0:

I am running an old AMD Ryzen 5 2400GE homelab with NFS
no XOSTOR or SDN.
Tested NTP Def and dhcp, ssh, wget, cont. repl. ...
all worked fine so far.

@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

@rzr said:
xo-lite: 0.18.0-1.xcpng8.3

Well I was and still is on v0.19.0:

I am running an old AMD Ryzen 5 2400GE homelab with NFS
no XOSTOR or SDN.
Tested NTP Def and dhcp, ssh, wget, cont. repl. ...
all worked fine so far.

I also have this problem in my XO-CE (ronivay-script) at home
I get the mail report after 4 days
A reboot resets the memory

the XO-CE have 3.1 GB and the Control domain memory have 2 GB
Node v24.13.1
Running Continuous Replication and Delta Backups

@acebmxer said in VM Pool To Pool Migration over VPN:

Maybe VPN overhead.

Have You checked the VPN capacity spec of Your firewalls?

No idea if anyone have "fixed" anything

No, the XO commit 5fcb6 hang for ~3 min at reboot today.
edit: I disabled the sceduled reboot yesterday.

@DwightHat
No
I did schedule a reboot of XO every morning and it seems it has worked because I "forgot" about it

No idea if anyone have "fixed" anything

I'm not running https and still on node v22

@Gheppy
My links from 6 to 5 works fine
Haven’t tested all of them of course, but quit a few and none of them have faild

I run these kinds of backup jobs

• Full Backup x2
• Delta backup
• Continuous Replication
• XO Config and Metadata

In ContRep, Conf/meta and in one of the Full Backup jobs I get Report when Never

But they are enabled in XO5 with mail address and Report when Skipped and failure

I fired up my 2nd XO wich is a ronivay script version.
Ran the update to latest commit 9f387
When I logged in, It start in the XO5 page
In my 1st XO "from docs", It start in the XO6

Maybe ronivay is not up to date with the new #release" of XO6
If You are running this type script, maybe that is the culprit

@probain Well I’ve been running commit 035ee for a few days now and haven't had any problems. But haven't done a lot of work with it.

When I update, I always run some kind of full/complicated update since I've had some problems before and with this type of update I've never had any issues.

sudo su
nvm install 22 && npm install --global yarn && cd ~/xen-orchestra/ && git checkout . && git pull --ff-only && yarn && yarn build --force && yarn run turbo run build --filter @xen-orchestra/web && systemctl restart xo-server.service && cd && systemctl daemon-reload

Or maybe just a simple CTRL F5 in Your browser will work