Doing a storage migration will change the VDI UUID in any case, so it won't be able to do a delta/incremental anyway

[{"name": "CPU Temp", "value": "39 degrees C", "event": "ok"}, {"name": "System Temp", "value": "31 degrees C", "event": "ok"}, {"name": "Peripheral Temp", "value": "46 degrees C", "event": "ok"}, {"name": "NIC Temp", "value": "59 degrees C", "event": "ok"}, {"name": "CPU_VRM0 Temp", "value": "43 degrees C", "event": "ok"}, {"name": "CPU_VRM1 Temp", "value": "34 degrees C", "event": "ok"}, {"name": "SOC_VRM Temp", "value": "44 degrees C", "event": "ok"}, {"name": "VDDIO_VRM Temp", "value": "48 degrees C", "event": "ok"}, {"name": "DIMMA~C Temp", "value": "45 degrees C", "event": "ok"}, {"name": "DIMME~G Temp", "value": "44 degrees C", "event": "ok"}, {"name": "MB 12V", "value": "12.08 Volts", "event": "ok"}, {"name": "MB 5VCC", "value": "5.10 Volts", "event": "ok"}, {"name": "MB 3.3VCC", "value": "3.35 Volts", "event": "ok"}, {"name": "VBAT", "value": "0x04", "event": "ok"}, {"name": "MB 5VSB", "value": "5.06 Volts", "event": "ok"}, {"name": "MB 3.3VSB", "value": "3.39 Volts", "event": "ok"}, {"name": "MB 1.8VSB", "value": "1.84 Volts", "event": "ok"}, {"name": "BMC 2.5V", "value": "2.47 Volts", "event": "ok"}, {"name": "BMC 1.8V", "value": "1.77 Volts", "event": "ok"}, {"name": "BMC 1.2V", "value": "1.19 Volts", "event": "ok"}, {"name": "BMC 1.0V", "value": "0.99 Volts", "event": "ok"}, {"name": "BMC 3.3VSB", "value": "3.28 Volts", "event": "ok"}, {"name": "CPU_SOC", "value": "1.22 Volts", "event": "ok"}, {"name": "CPU_VDDIO", "value": "1.12 Volts", "event": "ok"}, {"name": "FAN1", "value": "2100 RPM", "event": "ok"}, {"name": "FAN2", "value": "1960 RPM", "event": "ok"}, {"name": "FAN3", "value": "2100 RPM", "event": "ok"}, {"name": "FAN4", "value": "no reading", "event": "ns"}, {"name": "FANA", "value": "no reading", "event": "ns"}, {"name": "FANB", "value": "no reading", "event": "ns"}, {"name": "FANC", "value": "no reading", "event": "ns"}, {"name": "M2_SSD1 Temp", "value": "no reading", "event": "ns"}, {"name": "M2_SSD2 Temp", "value": "no reading", "event": "ns"}, {"name": "Chassis Intru", "value": "0x00", "event": "ok"}, {"name": "NVMe_SSD1 Temp", "value": "no reading", "event": "ns"}, {"name": "NVMe_SSD2 Temp", "value": "no reading", "event": "ns"}, {"name": "GPU4 Temp", "value": "49 degrees C", "event": "ok"}, {"name": "GPU6 Temp", "value": "34 degrees C", "event": "ok"}]

I can imagine that a fix could be to send "keepalive" packets in addition to the XCP-ng export-VM-data-stream so that the timeout on XO side does not occur

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

Thank you very much for sharing your findings Adding @Team-Documentation-Knowledge-Management and @Team-OS-Platform-Release to check what's next on our side

I had to disable Purge snapshot data when using CBT. Backups are not longer defaulting to full backups.

as @MBNext stated disabling Purge snapshot data when using CBT worked for me.

@uberiain at this point, when I am uninstall the old XCP-ng center software, and install the new msi, I just realized the xcp-ng keeps the settings file in Roaming folder. (C:\Users\user\AppData\Roaming\XCP-ng) When I deleted it I could re-register the servers.

@probain I would be interested in youre ansible role for deploying XO from sources

@zpvS9 said in Error installing windows PV drivers 9.0.9137: I have this error too installing the new PV driver, after uninstalling Citrix driver, reboot, execute XenClean, reboot again, it said that an unsupported device is still present. I must uninstall the device by showing hidden device in Device manager and the Windows PV driver now install. So adding this step in XenClean would be appreciated. encountered the same problem with hidden base system that i needed manually uninstall to get the tools to work.

@ph7 huh, that is weird. I'll try to troubleshoot more over the weekend. Thanks for pointing it out. @olivierlambert said in Upgraded RAM, It get's detected but not used. Any ideas?: I would first upgrade the BIOS of the motherboard. Consumer grade hardware is pretty buggy in general when you are using "advanced" features, sadly. That's the first thing i tried, no luck unfortunately

@dinhngtu Thanks. I did verify that it does not have the revoked version on any of the hosts. I've also verified that this is only occurring with Windows 2025. I can V2V Windows 2022 or any Linux distribution that we've tried, without secure boot issues. Also, a fresh installation of Windows 2025 doesn't have the issue. I've opened support ticket number 7747017 for this issue. Hopefully someone can get it figured out. Thanks. Allen B.