Hi, it's a known issue on newer CPUs: https://docs.xcp-ng.org/troubleshooting/windows-pv-tools/#bsod-0x3b-system_service_exception-on-newer-intel-cpus
What's your CPU Vendor value shown in xl dmesg?
Never mind, I missed your log: CPU Vendor: Intel, Family 6 (0x6), Model 143 (0x8f), Stepping 8 (raw 000806f8)
@kagbasi-wgsdac Blind guess, your ISO SR is not connected to one of the hosts?
@archw XenClean is not needed when upgrading; it's only needed when switching tools vendor, or when switching from the old XCP-ng 8.2 tools.
The XCP-ng 9.1 tools installer will block installation and indicate an error whenever XenClean is needed.
@probain Yes, that's expected as there were only changes in the installer and XenClean/XenBootFix, the drivers and guest agent binaries included in 9.1.145 and 9.1.146 are the exact same. As a result, the version information in the guest agent (which does the reporting) was not updated.
Hello all,
Version 9.1.146 Release of the Windows PV tools has been released.
Download the latest release here: https://github.com/xcp-ng/win-pv-drivers/releases
It will be integrated into the XCP-ng built-in tools ISO after a test period of 2 weeks.
This is a small revision to fix issues when installing on certain Windows installations. Only the installer and XenClean were changed; the binaries inside stay the same.
If you're already on 9.1.145, upgrading is optional.
Recent Windows patches also changed the exit code of schtasks.
A new package will be released to address this.
@manilx Interesting... It's checking for "ERROR: The system cannot find the file specified. -2147024894", which is why it's failing. What if you specified the command this way, with a backslash?
schtasks /query /tn \Copy-XenVifSettings /hresult ; echo $LASTEXITCODE
@manilx What do you see when you run this command from PowerShell?
schtasks /query /tn Copy-XenVifSettings /hresult ; echo $LASTEXITCODE
@manilx Can you check if there's a Copy-XenVifSettings task in Task Scheduler and delete it if it exists report back? Normally it's supposed to self-destruct but maybe something went wrong there.
@conitrade-as Sounds like a problem somewhere in the clipboard stack, I'll look into that.
@conitrade-as There should be a fix for that in 9.1.145. Could you try it?
Hello all,
Version 9.1.145 Release of the Windows PV tools has been released.
(Despite the name, it's still signed; I simply dropped the "Signed" moniker)
Download the latest release here: https://github.com/xcp-ng/win-pv-drivers/releases
It will be integrated into the XCP-ng built-in tools ISO after a test period of 2 weeks.
This release brings the new XCP-ng Standard VGA Display Driver as well as multiple bug fixes to all Windows drivers and guest tools components.
If you encounter installation/uninstallation errors, please try again with one of the following commands:
For installing:
msiexec.exe /i XenTools-x64.msi /log install.log
For uninstalling:
msiexec.exe /x XenTools-x64.msi /log 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.
Full Changelog: https://github.com/xcp-ng/win-pv-drivers/compare/v9.1.100...v9.1.145
Original build: https://github.com/xcp-ng/win-pv-drivers/actions/runs/23188455900
@MajorP93 AFAIK @teddyastie is working on a 1.0 release for Linux guests with this bug fix.
@MajorP93 Hi, are you using the Rust guest agent? We suspect that it's failing to rearm the ballooning feature after resuming from suspend.
@MajorP93 Thanks for the info, I'll need to discuss with the team first
@MajorP93 Hello, what does xe vm-param-get uuid=... param-name=memory-target say on your VM after migrating?
@acebmxer process 1775 (unattended-upgr<ade>) is your hint. Your VM was presumably running an unattended upgrade while you were trying to install the tools.
@rniesen Do you mean occasional hangs? Yes, Server 2025 is known to hang if these options are not present.
@rniesen Your VM is missing Viridian extensions (Hyper-V-compatible VM enlightenments implemented by Xen). This is typically due to the wrong VM template being chosen at the time of creation; the built-in Windows template should be used for all Windows VMs. There's an issue with Server 2025 that causes it to not run well without these features enabled.
Please power off your VM, run this command to add them back, then reboot:
xe vm-param-set uuid=<vm-uuid> platform:viridian=true platform:viridian_time_ref_count=true platform:viridian_reference_tsc=true platform:viridian_apic_assist=true platform:viridian_crash_ctl=true platform:viridian_stimer=true