@probain said in XCP-ng Windows PV tools announcements:

No problem... If you ever decide to have the .exe-file as a separate item. Not bundled within the zip-file. Then I would be even happier. But until then, thanks for everything!

The guest agent EXE is just one part of the tools package (and actually may not have the same version as the MSI file), therefore I don't think it should be relied upon for versioning. I recommend using the product_id method instead.

@Johny said in XCP-ng Windows PV tools announcements:

Both versions of XCP-ng Center are returning a Management Agent not installed error under the Used Memory column when using the 9.1 driver (this was also an issue with the previous 9.0 version).

Although, XOA does show that it's installed. Is this a known issue?

Looks like XCP-ng Center decided to detect the guest agent in a different way, namely checking for the feature "feature-static-ip-setting" which is XenServer specific (and, as indicated by the name, should not be used for management agent version checking). Please open an issue on the XCP-ng Center repo for this.

The cosmetic issue about management agent version disappearing after migration/resume has already been fixed in 9.1.100.

@probain The canonical way is to check the product_id instead https://docs.ansible.com/projects/ansible/latest/collections/ansible/windows/win_package_module.html#parameter-product_id The ProductCode changes every time a new version of XCP-ng Windows PV tools is released, and you can get it from each release's MSI:

@dom0 Yes, the Vates tools are our recommended guest tools for XCP-ng going forward.

Hello all,

Version 9.1.100 Release Signed 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 release brings multiple bug fixes to all Windows drivers and guest tools components.

To download XenClean, click here. The installer downloads also includes a copy of XenClean and XenBootFix. Remember to carefully read XenClean docs before use.

Before installing

Thank you for using our Windows PV tools. Please carefully read the instructions below.

• Not compatible with the "Manage Citrix PV drivers via Windows Update" option. You must disable this option before installing.
• We recommend creating backups/snapshots before installing.

Changes since 9.0.9137

• NEW: Add installer option to disable time sync.
• NEW: SBOM is now included with the installation package.
• Improved: Better cleanup of Xenbus devices.
• Fixes: Driver symbols are now back after an accidental omission in 9.0.9137.
• Fixes: Fix restoration of network settings after uninstallation.
• Fixes: Fix XenClean in Safe Mode.
• Fixes: Fix system time drifting when time sync is enabled.
• Fixes: Fix display of Windows OS version.
• Fixes: Fix Xen Guest Agent reporting on VM resume.
• Fixes: Fix receive-side scaling.
• Fixes: Various driver stability fixes.

Help / Community support

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.

Additionally, please report any errors or BSOD you encounter during testing of this release. Your feedback is very appreciated.

• Discussion: https://xcp-ng.org/forum (preferred)
• Issue Tracker: https://github.com/xcp-ng/xcp/issues
• IRC: #xcp-ng and #xcp-ng-dev on irc.freenode.net

Full Changelog: https://github.com/xcp-ng/win-pv-drivers/compare/v9.0.9137...v9.1.100

@dom0 They are built from scratch using these components:

• Upstream Xen Project PV driver sources, which includes contributions from Citrix, Vates, Invisible Things Lab among others, and where we are one of the maintainers;
• The Rust guest agent, which is developed by us;
• The installer, packaging and tooling is completely our own.

The main repo is here: https://github.com/xcp-ng/win-pv-drivers

@flakpyro It's a known issue, a new version with fixes will be released soon.

@kevdog Try adding console=ttyS0 earlyprintk=serial,ttyS0. You shouldn't need hvm_serial, xl console should be enough. Make sure that the boot parameters show up correctly in grub.

@mickwilli Did you try the tweaks I've posted above?

@mickwilli Is it still the same issue? If it's intermittent and resolves after a few minutes, it might be hardware-related.

Thanks for the information.

@Chico008, does the information at https://xcp-ng.org/blog/2025/10/30/xcp-ng-8-3-varstored-update-unbootable-vm-risk-and-remediation/ resolve the issue for you?

@acebmxer Did the fix-efivars.py script fix the Ubuntu installation issues for you? If so, which version of varstored do you have, did you install varstored 1.2.0-3.3 following our blog post?

@linuxmoose The guest Secure Boot situation needs some fixing from our end (see https://xcp-ng.org/blog/2025/10/30/xcp-ng-8-3-varstored-update-unbootable-vm-risk-and-remediation/ for context). I can produce for you a test update which resolves all known problems and makes guest Secure Boot work again if you wish.

@Chico008 said in XOA - Vm linux install keep failing since updateing XCP to 8.3:

tried using uefi (non secure) or bios, each time install failes.

ISOs comme from my NAS, and VM disk are hosted on a ISCSI Lun

on 8.2 was exactly the same conf, sources, all worked fine, but now i can't :/, and i'm unable to understand the report, i only it failed during kernel install.

my Isos are the same i used for 8.2, on the same NFS Share.

tried installing a win 2K19 server, seems ok, but Ubuntu server can't (even tried a ubuntu server 22, same)

Reply

Could you post the ISO version you were using for the installation and hardware details?

@acebmxer Could you fetch and send the error report somewhere?

@lastcmaster Hi, it's a known issue that guest agent versions are not reported after migration or suspend. Other functionalities (poweroff/reboot, suspend, network change etc.) should continue to work normally.

@flakpyro said in VM start stuck on "Guest has not initialized the display (yet).":

@dinhngtu said in VM start stuck on "Guest has not initialized the display (yet).":

You must run secureboot-certs clear if you're updating from 1.2.0-2.4 or 1.2.0-3.1 and have previously run secureboot-certs install with the above versions installed.

Should we run this before installing the update or after 1.2.0-3.2 has been installed?

You should run that preferably after updating all hosts.

@lukasz_s said in VM start stuck on "Guest has not initialized the display (yet).":

@dinhngtu thanks for advice

i've upgraded varstored and varstored-tools:

rpm -qa | grep varstored
varstored-1.2.0-3.2
varstored-tools-1.2.0-3.2

than i've cleared varstore with secureboot-certs clear
should taht folder contain more files ?

ls /usr/share/varstored/
KEK.uth
PK.auth
db.auth

what about dbx file ?

That file is not shipped with varstored nor needed for now. We're validating the final 1.2.0-3.2 and preparing our guidance for the official update.

@acebmxer All looks good from the output. There might be some VMs that need fixes for Windows dbx updates to work properly, I'll try to add that in the official version.

@acebmxer Yes, that'll fix the situation.

Note that we're discussing a different approach for the official update, which will involve using a manual repair tool.

@flakpyro said in XCP-ng 8.3 updates announcements and testing:

@dinhngtu The output of that command seems to result in the output of "Scanningn every UUID in my pool", most of which do not use SB. Im guessing that normal and i do not have any affected VMs any longer?

Yes, it'll produce an error message in unserialize_variables when there's a problem.

@acebmxer Scanning on 1 host will scan the whole pool at once.

In the output you posted, there's only c81f1f1b-9f95-38ec-f96e-5ce8fea073e6 which needs fixing.

@acebmxer You can confirm if there are other affected VMs using this command:

xe vm-list --minimal | xargs -d, -Ix sh -c "echo Scanning x 1>&2; varstore-ls x" > /dev/null

If there are still affected VMs, you must fix them on varstored-1.2.0-3.2 by secureboot-certs clear + propagating before downgrading to 2.3 (if you wish).

Note that downgrading to 2.3 with pool certs cleared means you'll need to set up guest Secure Boot again. So I recommend staying on 3.2 if it's possible for you.