@stormi Microcode updated on affected Gen11 i7. Running normally.

@gduperrey I jumped in all the way by mistake... I updated a wrong host, so I just did them all. Older AMD, Intel E3/E5, NUC11, etc. So far, so good. Add/migrate/backup/etc VMs are working as usual. Good for guest tools too, but mine are mostly Debian 7-11. Stuff is as usual so far.

I agree and I'll say it again, Thanks! It's not just Linux/Xen stuff. It is XCP-ng and XO that make everything work as a cohesive vertical open-source solution (some nice buzz words). Thanks to the Vates team and community that have built and support it. I look forward to ongoing continuous improvement and innovation!

@bleader Installed and running.

@bleader Updates running on several old and new intel machines (including microcode update). Working fine so far. Rolling Pool Reboot is a helpful feature.

@bleader I installed it on a bunch of busy hosts. All are fine, but none used PCI passthrough. The Rolling Pool Reboot in XO was very helpful.

@dinhngtu On a quick test, the ISO boots and installs. When the VM boots from the HD it crashes (and on reboots).

Updating XCP 8.3 with qemu-4.2.1-5.2.12.2~fixvwc1.1.xcpng8.3.x86_64 solves the issue and the installed windows image boots correctly without any additional changes.

@abudef @olivierlambert @thomas-dkmt I agree. I read block the same way... how about disable or prevent. (French? empêcher)

@julien-f @olivierlambert

Thanks for the ability to delete XO task logs feature! (XO commit f6e6e)

@gduperrey Installed and running on Intel systems, and Zen3 system that sees the microcode update.

@gduperrey The new OpenSSL/SSH blocks existing/working RSA keys from older SSH clients. While you can still use a password for SSH, it will block old keys from working which will break things (not good for existing LTS installs). To maintain compatibility add PubkeyAcceptedAlgorithms +ssh-rsa to /etc/ssh/sshd_config

@Pa3docypris I also had this problem with one single Debian VM. I would delete the snapshot and they would just keep adding every backup. I have lots of the same VMs and lots of other VMs on the pool. Three VMs were basically exactly the same but only one had an issue.

I tried deleting all snapshots on the VM. Changing the CBT state. Doing a full backup up of the VM.... same problem. Snapshots just built up.

I found a CD in the VM drive and it would not eject (with a XCP error). So there was something strange with the VM state. I shutdown the VM, cleared the CD, and restarted the VM. After that, backups worked normally for that VM. So I won't blame XCP or XO, it seems the VM was just in a random strange state that caused problems.

@dcskinner @acebmxer I totally agree.... XOA is the Vates provided software appliance XO system.

Compiling XO yourself is XO from source or XO community edition or anything other than XOA. Calling it XOA adds confusion because it's not the same thing that Vates provides.

@MajorP93 @olivierlambert I think 8.3 has reached LTS so I don't think the drivers are getting major upgrades (it's up to Vates). It seams reasonable to add the 8125 alt driver and new 8126/8127 drivers as an installable option.

Realtek keeps releasing new chips and new versions of the existing chips (like the 8125 in @paha machine) that don't work with the existing older drivers. It's an ongoing issue even with mainline Linux kernels.

@paha Try installing r8125-module-alt from my web page.

@whyberg Nope... that feature is part of the CPU. But is that the actual problem? Maybe... As that machine is too old to do any real work, it's a fine toy. There are better faster cheap test machines available.

@florent Delta backup is also leaving old snapshots on some VMs. It should only have one (current) snapshot for the nightly backup. This is an issue on 1 of 100 VMs.

XCP (Jan 2026 update) and XO (91c5d) are current.

@whyberg Normally not 10x...

@whyberg The E5430 does not support EPT/SLAT.... without EPT the system uses shadow paging so virtual machines will be slower. Also, you can't run XCP 8.3.

@florent Yes.