@vxgmichel The new dom0 kernel version installed fine on my lab pool and everything appears to be running well.
Posts
-
RE: XCP-ng 8.3 updates announcements and testing
-
RE: XCP-ng 8.3 updates announcements and testing
@dinhngtu Thank you for bringing the TPM platform validation profile to my attention. I see that there is yet another nuance to the firmware boot process I didn't fully understand. I'm going to dig into those TPM group policies to see what that's all about. (Later on . . .) Found them, here:

-
RE: XCP-ng 8.3 updates announcements and testing
@lmolina Latest update candidate edk2 fix applied without issue to my four host home lab pool. I tested one BitLocker encrypted Windows 11 VM with full shutdown and restart. What surprised me is that the VM booted back up fine. I was expecting that anything that changed the Tiano UEFI guest firmware might bork BitLocker unless it was suspended prior to applying the hypervisor host fix. (e.g. PowerShell Suspend-BitLocker -MountPoint "C:" -RebootCount 0 suspends BitLocker for an infinite number of guest reboots until it is explicitly resumed.) Apparently, this particular update doesn't alter any part of the guest firmware that causes a noticeable change to BitLocker. As a result, the boot volume unlocks and boots normally. Note that a firmware update on a physical machine generally is noticed by BitLocker. This is the reason the OEM's firmware installer suspends BitLocker with RebootCount 1 before performing the update's finishing reboot.
-
RE: XCP-ng 8.3 updates announcements and testing
@gduperrey @lmolina All, While I sympathize with @manilx 's point regarding the rapid-fire updates, we are living in the age of AI agent attacks at the inhuman speed of automation. With that in mind, I am personally appreciative of your zest for releasing critical updates as soon as possible. My security group released a compliance notice today regarding CVE-2026-98432 and I was grateful to be able to tell them that the fix had been released yesterday. Keep on keeping on, Vates!
-
RE: XCP-ng 8.3 updates announcements and testing
I deferred applying the preview patches this time in order to try my luck again with RPU. Unfortunately, it did not work for me again as it has not in the past. My results are similar to others here: primary host patch application went fine including the reboot. However, once it began doing a secondary host, it started throwing errors e.g. CANNOT_EVACUATE_HOST and VM_REQUIRES_SR etc. However, manually putting the host in maintenance mode from the GUI evacuated each host just fine and I was able to apply the patches and reboot each subsequent host from the XO GUI. Also, as with others here, the RPU task hung in the task list and even a reboot of the XO VM would not clear it forcing me to delete the task using xo-cli e.g. xo-cli rest del tasks.
ENVIRONMENT: Home lab consisting of 4 x Dell OptiPlex 7040 i7-6700 SFF hosts, 48GB RAM each, 10 Gbps storage connections to a TrueNAS home-built NAS via NFS and XO from source (XOS) using @ronivay build script on AlmaLinux 10.2 minimal install VM with XO commit 6a441 compiled on 2026-08-28 from master branch. FWIW, RPU functionality remains unavailable to me, though obviously, this is not a showstopper for a 4 x host home lab pool. If there is anything I can do to help resolve this, please let me know as I remain an enthusiastic proponent of the Vates virtualization stack. -
RE: XCP-ng 8.3 updates announcements and testing
Applied the latest candidate updates to my four-node pool home lab. The once or twice that I previously tried the RPU feature, it didn't work for me so have since performed the updates from the dom0 CLI followed by properly sequenced manual host reboots. (I'm happy to try RPU in any future update where correcting that functionality is a focus.) Post update, everything appears to be working well including live migration during which the VM is deliberately made busy e.g. Windows and Linux updates; taking and deleting snapshots and tailing the SMlog to see if any GC errors occur. (Didn't see any.) I also like the new XCP-ng VM firmware boot logo. That's a nice touch as it further emphasizes Vates' commitment to the platform from the firmware on up. That's good marketing! All in all, this looks like a solid set of updates.
-
RE: XCP-ng 8.3 updates announcements and testing
Applied the latest batch of updates with no apparent problems.
-
RE: XCP-ng 8.3 updates announcements and testing
Updated my four host home lab pool with latest batch of updates with no observed issues.
-
RE: XCP-ng 8.3 updates announcements and testing
Installed latest updates on my four host home lab pool and a fifth standalone host with no apparent issues.
-
Citrix Releases New XenServer SDK 25.30.0 - 15-Sep-2025
Citrix just released an updated XenServer SDK with support for C, Microsoft .NET, Go, Java, PowerShell and Python. Likely useful for XCP-ng developers and users as well.
-
RE: Win11 24H2 install fails consistently
@markr All, I am currently running Windows 11 24H2 on an Intel Haswell i7-4700HQ laptop and it runs fine. What's more, it was in-place upgraded from Windows 11 23H2 using the (still working) setup.exe /product server switch compatibility bypass. (Simpler than all the LabConfig registry tweaks.) The only change I know of that simply won't run due to 24H2 is that it requires a processor capability that has been available since first generation Intel Core processors. It should run on your hardware in a VM. Seems like something else is going on.
-
RE: Pass Through of USB Storage Adapters Not Working
@JanP Thanks for the nice cookbook! I set up the passthrough SR per your instructions and then added the VUSB to the VM and started it up. As before, when I attach the disk to a USB 2.x port, I see it and it works. However, when I then plug it into a USB 3.x port and recreate the VUSB on the shutdown VM, it correctly shows USB 3.x with 10000 speed, but my Windows 11 VM does not see it. The Windows device manager shows that there is no USB 3.x device controller, only USB 2.0. Is there a way to force the emulated USB device in the VM definition to be USB 3.x? If Windows finds a USB 3.x device, it will autoconfigure it. Unfortunately, it doesn't appear to find a USB 3.x device. Just for fun, I'm running my test on a tiny Beelink EQ13 PC with Intel N100/4C,16GB/500GB SSD/2x1Gb Realtek NICs that runs XCP-ng 8.3 with 2xVMs: XOS and Windows 11 24H2. It's a $189 box I acquired in July of 2024 and I've been having a blast bending it like Gumby for different uses.
-
RE: Pass Through of USB Storage Adapters Not Working
All, I have never been able to successfully pass through a USB 3.x storage device (like a USB hard drive) to an XCP-ng 8.2/8.3 Windows VM. However, USB 2.0 devices such as a license dongle; that works. I, for one, would love to see this get fixed. FWIW, yet another "me too."
-
RE: XCP-ng 8.3 updates announcements and testing
Latest urgent updates installed on 3-node Intel pool. Everything is working as before including the pre-production code "no stats" issue, but that still resolves following xe-toolstack-restart command. Since it is currently Microsoft patch Tuesday here, the latest Windows 11-24H2 2025-05 cumulative update was installed to VM along with various Linux VM updates and live VM host migrations. All working well including latest af03c Xen Orchestra from source (XOS).
-
RE: [RHEL kernel bug] XCP vm fails to boot after newest kernel applied.
@Greg_E Maybe it only affects Intel? That would be a new wrinkle. Perhaps other AMD users can confirm if the latest AlmaLinux 8 kernel runs fine on their AMD XCP-ng 8.3 hosts? Just read the above referenced RedHat bug report here: https://access.redhat.com/solutions/7116307 Sure enough, it says Xen + Intel in problem description. Check it out.
-
RE: [RHEL kernel bug] XCP vm fails to boot after newest kernel applied.
@Greg_E Wondering what might be the difference? I am using the XenServer Linux tools version 8.4.0-1 and BIOS boot firmware.
-
RE: XCP-ng 8.3 updates announcements and testing
Latest test updates applied to 3-host Dell OptiPlex 7040 SFF (i7-6700) pool. Upgrade went smoothly and everything appears to be working normally. I did notice the flatlined stats issue mentioned previously, but the xe-toolstack-restart seemed to bring those back to life. Thanks @Greg_E and @abudef for catching and addressing that.
-
RE: [RHEL kernel bug] XCP vm fails to boot after newest kernel applied.
This is just a "me too" reply to indicate that I am also experiencing the boot failure immediately after upgrading AlmaLinux 8.10 to the latest kernel 4.18.0-553.50.1. Hopefully, the kernel fix will get integrated soon into the affected and popular RedHat 8 derivatives so that Alma and Rocky 8 et al. can continue to run on our favorite hypervisor. This is a bad one.
-
RE: Windows VMGuest changing network cause the guest to crash
@piotrlotr1 Will definitely use the trick if needed in the future. Normally, changing the network for a running VM is not something we typically need to do. Thanks!