@tsukraw There's no need to uninstall the old version, the upgrade is enough.
The feature to disable time sync is also just a convenience shortcut for setting the TimeSyncMode value in HKLM\SYSTEM\CurrentControlSet\Services\xenagent to a DWORD of 0. You can set it manually or through Group Policy if you wish. (In fact, GPO might be a better solution on domain environments)
@McHenry Turning off the Manage via Windows update first + tools uninstall + reinstall should take care of it.
@McHenry I think the detection is accurate in your case. Have you checked the driver versions in Device Manager? See https://docs.xcp-ng.org/troubleshooting/windows-pv-tools/#xenserver-vm-tools-not-upgrading-drivers-after-installation
@mickwilli Do you know what solved the issue, was it the tsc_mode=2+nomigrate=true one or was it a Windows update?
@acebmxer The Recommended actions section of the guest Secure Boot docs has been updated with our latest recommendations. In short, VMs existing prior to the varstored update will need to have their Secure Boot certificates updated with the Propagate certificates button.
@ovicz Ok, I've contacted the storage team for a look.
@ovicz How about xe vdi-list sr-uuid=8e908932-0577-d6f0-3133-14d94a317b90 ?
@ovicz I'd start by listing the VDIs on your SR to see if things are still there.
@ovicz To confirm, you were using the ZFS integration documented here https://docs.xcp-ng.org/storage/#zfs right?
@ovicz How is your SR connected to the host, via NFS or something else?
@ovicz No UEFI mapping displayed in the shell suggests that the VM couldn't detect its disks. Is your SR doing OK?
@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 installederror under the Used Memory column when using the9.1driver (this was also an issue with the previous9.0version).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.
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 /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.
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:
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?