@cg Does it show up in XO? I noticed it doesn't show in "Add a new VM" in XO Lite either.
In a pinch, this command should work:
xe vm-cd-insert vm=... cd-name=guest-tools.iso
I haven't tried XCP-ng Center.
@cg Does it show up in XO? I noticed it doesn't show in "Add a new VM" in XO Lite either.
In a pinch, this command should work:
xe vm-cd-insert vm=... cd-name=guest-tools.iso
I haven't tried XCP-ng Center.
@flakpyro Hello,
Normally, an upgrade will remove the old product code so that it should no longer be present to block the upgrade, so I was surprised to see both product codes installed. I'll try to reproduce.
Hello,
The hang bug will be fixed in a future release of Xen, but Windows requires enabling all Viridian extensions (currently 6) to ensure optimal performance and reliability. Enabling Viridian extensions also fixes the hang bug via a different way.
On Windows guests, please reenable all Viridian extensions using these instructions: https://docs.xcp-ng.org/vms/#enabling-viridian-extensions
Hello all,
Version 9.2.445 of the XCP-ng Windows Guest Tools has been released.
Download the latest release here: https://github.com/xcp-ng/win-pv-drivers/releases
This release brings important bug fixes to the Windows drivers and installer.
Important note for users upgrading from 9.2.350: You must first install the XenTools-fix-9.2.351.msp hotfix to upgrade to 9.2.351 before installing 9.2.445. Otherwise, upgrades from 9.2.350 will be blocked. Reboot is not required after installing the hotfix.
The installer downloads include a copy of XenClean and XenBootFix. It is not necessary to run XenClean when upgrading from previous versions of the XCP-ng Windows guest tools, unless prompted by the installer. Remember to carefully read XenClean docs before use.
Note: Always download the latest XenClean/XenBootFix from https://github.com/xcp-ng/win-pv-drivers/releases . You can find them in the latest release ZIP/ISO archives.
Thank you for using our Windows PV tools. Please carefully read the instructions below.
If you encounter installation/uninstallation errors, please try again with one of the following commands:
For installing:
msiexec.exe /i XenTools-x64.msi /l*vx install.log
For uninstalling:
msiexec.exe /x XenTools-x64.msi /l*vx uninstall.log
Please include this log along with the file C:\Windows\INF\setupapi.dev.log in your bug report. These files will help us troubleshoot any installation issues.
Additionally, please report any errors or BSOD you encounter during testing of this release. Your feedback is very appreciated.
@XCP-ng-JustGreat Windows VMs will pass the Measured Boot check even after an edk2 update if BitLocker is set up to only use Secure Boot for integrity validation (see the "Configure TPM platform validation profile for native UEFI firmware configurations" policy, PCRs 7 and 11)
@fred974 Hello,
Could you please provide the logs produced by XenClean after its execution?
If your VM couldn't boot after XenClean, XenBootFix executed from a recovery environment should get your VM working again.
Instructions are available here: https://docs.xcp-ng.org/troubleshooting/windows-pv-tools/#windows-fails-to-boot-hangs-inaccessible_boot_device
@acebmxer Hello, could you look into the xen and kernel logs for errors?
@cg @trelane I've updated the release notes and added a link to the 9.2.351 patch.
For the IP loss bug when toggling the "Manage Citrix PV..." setting, this bug should not happen on XCP-ng tools. In theory, it should not happen on the XenServer 9.6.0 drivers either, but I haven't tested.
If you need to reconfigure your VM's IP, check out the commands xe vif-configure-ipv4/ipv6. Currently it supports configuring IP/prefix/gateway; DNS configuration is coming soon.
@john.c Indeed I skipped over the part that the host is still on 7.6, that's a rather big upgrade blocker I think.
Also, I'd recommend upgrading to Server 2019 or even Server 2025 if that's feasible, since support for Server 2016 is ending soon anyway.
@hrvojer You should remove old tools before doing an in-place upgrade because the older ones are almost guaranteed to cause upgrade failures or BSODs if they're still installed when the upgrade takes place. Also note that removal of older tools (and installation in some cases) will wipe out your static IP config if you happen to depend on it.
@hrvojer Ever since 2012 R2 went out of support, there have been multiple compatibility breaks in the drivers and guest agents since they now target Server 2016+. It might be possible to get the drivers working on 2012 R2 in a testing environment, but bringing that to production is another topic.
@hrvojer I can't tell for sure without detailed troubleshooting, but your crash reminds me of a bug in XenVbd that was fixed in the XCP-ng 9.1.200 tools (Apr 2026). It's unlikely that updating to an old Xen tools version would help in that case.
@hrvojer There are many bugs in older versions of the Xen PV drivers. I suggest running Windows without guest tools and drivers if you can take the performance and functionality hit (no suspend/migration on UEFI VMs, no metric reporting, etc).
Hello, this issue has been fixed in XAPI 26.1.19-1.1 available in the testing updates. For now you have to configure your VMs manually (https://docs.xcp-ng.org/troubleshooting/common-problems/#pci-passthrough-error-unsupported-msi-delivery-mode-7) but the fix will be activated by default in the future.
@ovicz Which exact version of XAPI do you have? If you have 26.1.19-1.1 from testing, you should be able to fix it by setting hvm-pirq=false using the instructions here: https://docs.xcp-ng.org/troubleshooting/common-problems/#pci-passthrough-error-unsupported-msi-delivery-mode-7
@ovicz Have you set platform:hvm-pirq=false on it? The disable-by-default behavior had to be reverted in the upstream fix because of an unforeseen regression.
@flakpyro Note that various important Viridian settings are not yet settable via Xen Orchestra, so you might want to confirm using xe instead.
@flakpyro These template updates only concern new "from scratch" VMs. Older VMs should not be impacted at all.
But if some of your VMs are missing Viridian settings, you may run into poor performance and/or odd Windows issues. You can correct them using the instructions documented here: https://docs.xcp-ng.org/vms/#enabling-viridian-extensions
@ovicz I was wrong, it's already in testing. So you could simply install the testing updates for that.