@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

@gduperrey
All good so far

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

https://xcp-ng.org/forum/topic/11951/just-fyi-current-update-seams-to-break-nut-dependancies

updated to f5468 and it seems to work fine in my home lab lab
I will update my homelab "production" later

I have retention of 2
In XO I only see 1 VM and I think this is intended
I get 2 snaps and I can restore 2 different VMs from them

I think You nailed it

edit: And delta is back

@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

ph7 said:

Local VMs vith scheduled Incremental Backup and CR are affected
NFS VMs vith scheduled Incremental Backup are affected

Incremental -> Incremental OR full

@rzr

@florent
fix_flr commit b7230
Restored files from debian 12 on local ext
and from Linux Mint 22.3 on NFS
both with tgz and zip

Local VMs vith scheduled Incremental or full Backup and CR are affected
NFS VMs vith scheduled Incremental or full Backup are affected
NFS VMs with CR not affected

@julienXOvates
The faulty ones are on local SR
If I take a manual snapshot on a NFS VM, I see the correct value

Will test a scheduled one

same in my XOA 6.5.1

@julienXOvates
Well not in my daefc witch is newer than 6.5.1

ph@romy:~$ df -h
Filsystem      Storlek Använt Ledigt Anv% Monterat på
udev              1,9G      0   1,9G   0% /dev
tmpfs             392M   916K   391M   1% /run
/dev/xvda2         93G   6,3G    82G   8% /
tmpfs             2,0G      0   2,0G   0% /dev/shm
efivarfs          128K    52K    72K  42% /sys/firmware/efi/efivars
tmpfs             5,0M      0   5,0M   0% /run/lock
tmpfs             1,0M      0   1,0M   0% /run/credentials/systemd-journald.service
tmpfs             2,0G   4,0K   2,0G   1% /tmp
/dev/xvda1        975M   8,8M   966M   1% /boot/efi
tmpfs             1,0M      0   1,0M   0% /run/credentials/getty@tty1.service
tmpfs             1,0M      0   1,0M   0% /run/credentials/serial-getty@hvc0.service
tmpfs             392M    68K   392M   1% /run/user/105
tmpfs             392M    68K   392M   1% /run/user/1000

seems more like 8% to me

@rzr
It seems to be working
edit: the update that is.

In the back of my head I knew there was a thread and I found it
https://xcp-ng.org/forum/topic/12040/restore-only-showing-1-vm/21?_=1780396449511

Maybe this schould be under XO/Backup
Anyhow.

ph7 said:

Ran the 2 updates released today and...
Back to only showing one VM in Backup/Restore as it did a month or 2 ago.
Ran the replication job and all VMs showed up in Backup/Restore again. (XO5)

It occurred again today, only showing 1 VM in restore
XO daefc
Host updated 2 weeks ago.
After 1 scheduled CR job ran all VMs showed up again