-
We reserved a PCI ID (if I remember correctly), so it's more about asking Microsoft to put it in their update system. I have no idea if it's feasible for us.
-
I was thinking more of updating the entire set of the agent and drivers, similar to how XenServer VM Tools for Windows have it implemented. Using a scheduled job, they regularly check whether an update is available, and if so, they carry out the update of both the agent and the drivers themselves.
-
@dinhngtu said in XCP-ng Windows PV tools announcements:
@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:
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!
-
Management Agent not installed in XCP-ng Center
v20.04.1and25.4.0Hi team,
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?
XCP-ng Center:
XOA:
VM using XenServer's version, for comparison:
Management agent9.4.2-178
-
@Johny said in XCP-ng Windows PV tools announcements:
Although, XOA does show that it's installed. Is this a known issue?
Yes it's a known issue, only cosmetic and the next driver update will fix it
-
@olivierlambert thanks for the quick reply!
-
@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.
-
@dinhngtu Seems like an issue for this already exists: https://github.com/xcp-ng/xenadmin/issues/260
Added what I wrote above as a comment.
-
Just wanted to add a comment:
Thanks for continuing to release the drivers in an ISO. I was having some slowness with the 9.0.9 versions that are currently included with XCP-ng, this is a new Windows 11 25h2 that I'm working with to prototype a workflow in my lab. I just grabbed the 9.1.x ISO from Github and copied it to my ISO SR and installed. There seems to be a slight performance increase in this Win11 VM. That said, 25h2 is horribly bloated with junk, so much so that I think I'm going to need to strip a bunch out before I put this version into production. This might be a condition for MicroWin customization.
Or maybe add a couple of things to the LTSC version (we have licensing for this at work).
-
@Greg_E said in XCP-ng Windows PV tools announcements:
Just wanted to add a comment:
Thanks for continuing to release the drivers in an ISO. I was having some slowness with the 9.0.9 versions that are currently included with XCP-ng, this is a new Windows 11 25h2 that I'm working with to prototype a workflow in my lab. I just grabbed the 9.1.x ISO from Github and copied it to my ISO SR and installed. There seems to be a slight performance increase in this Win11 VM. That said, 25h2 is horribly bloated with junk, so much so that I think I'm going to need to strip a bunch out before I put this version into production. This might be a condition for MicroWin customization.
Or maybe add a couple of things to the LTSC version (we have licensing for this at work).
Download the full Windows 11 ISO then use Microsoft Windows ADK. To customise, strip down unwanted parts, including appx provision packages and slipstream in drivers and/or msi installers.
If your using a high enough edition of Windows 11 version 25H2 don’t forget the new GroupPolicy option to remove default packages!
