Vates group | XCP-ng and XO forum

dinhngtu

Hello all,

Version 9.2.385 Release of the 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, installer and XenClean.

Important note for users upgrading from 9.2.350: You must first install the included XenTools-fix-9.2.351.msp hotfix to upgrade to 9.2.351 before installing 9.2.385. Otherwise, upgrades from 9.2.350 will be blocked. Reboot is not required after installing the hotfix.

To download XenClean, click here. The installer downloads also includes 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

Before installing

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

It is not necessary to run XenClean when upgrading from previous versions of the XCP-ng Windows guest tools, unless prompted by the installer.
Not compatible with the "Manage Citrix PV drivers via Windows Update" option. You must disable this option before installing.

Changes since 9.2.350

Improved: Update XenClean to .NET 10. XenClean is now a native binary that no longer requires .NET Framework.
Fixed: Fix data corruption issue during in-memory snapshots and backups.
Fixed: Fix DLL sideloading issue in XenClean.
Fixed: Fix driver migration during upgrades.
Fixed: Fix display of IPv6 addresses in Xen Orchestra in some situations.
Fixed: Reliability and stability fixes for the drivers and guest agent.

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 /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.

Emmanuel V

It might be worth adding a message in XO at export, or in the documentation ?

pierrebrunet

@Andrew Hi,
I am on it, thank you for the report!

poddingue

Thanks a lot for your feeback, folks!

Danp

It's possible that the issue lies within VMware Workstation.

Danp

Have you attempted to analyze the exported file using qemu-img?
For example:

qemu-img info file.vmdk
qemu-img check file.vmdk

poddingue

I gave this a go on my lab XOA, and XO isn't touching your option at all: the failure quotes the command it ran, mount -o sec=krb5p -t nfs <server>:/path /run/xo-server/mounts/<remote-id>, and a control remote with no custom options mounted the same export fine.

It does fail with mount.nfs: an incorrect mount option was specified, but that line tells you less than it looks like: I fed it sec=totalnonsense and got the identical message back, which is why it reads like XO refusing a valid option when it's really just relaying what mount.nfs said.

The appliance ships rpc.gssd as part of nfs-common, so that part's there. What isn't there is /etc/krb5.keytab or /etc/krb5.conf, and the systemd unit carries ConditionPathExists=/etc/krb5.keytab, so the daemon never starts. Mine last failed that condition at boot eleven days ago and said nothing about it.

I went one step further: dropping a keytab in place is enough for rpc.gssd to start and stay up, so that condition really is the only thing stopping it, and it doesn't need krb5.conf for that. Whether the mount then works needs a KDC and principals that agree with each other, and I couldn't get that far, so that part is still untested.

Danp

Ah... ok. I think I originally checked the VM export.

This could be a bug. Does it occur with all VDIs? What happens if you try to import the file back into XO?

Danp

@abudef What steps are you performing to export the VDI as a VMDK?

Vates

Posts

Before installing

Changes since 9.2.350

Help / Community support

Member List