XCP-ng Windows PV Drivers 8.2.2
Don't use both! From Windows updates, they are Citrix drivers. They can enter in conflict with ours. Despite the code is the same, the signature is not and they probably can compete each other.
Well then that is the problem. The "Get Windows Update" is defaulted to "On" I think. I didn't know they essentially do similar things.
I need to create a new VM then and make sure I turn off that feature before booting the Win 10 image. Then I can install your set.
It's not defaulted on "on", except if it's a custom template. If you chose to have Windows update driver, then don't install PV drivers manually.
I did a test on my side: works well with our driver package:
Mine shows "Allow Windows update" or something similar and I didn't enable that.
I know I used a template. I'll remove and recreate the VM and see if it defaults the Win update setting.
I appreciate you checking. Good to know it's working. I just need to see why Windows update pulled it in.
Is there any difference between the two or is it same things with different names?
Yes, just leave "Windows Update tools" disabled, that's it
Thanks Olivier. Loving the lab I setup so far. Really impressed with the entire infrastructure you guys have managed to put together.
@olivierlambert So I just created a new Win 10 VM and made sure to use the template. I created this VM in the XCP-NG XenCenter. I then went into XOA and "Windows Update Tools" is checked to the on position by default.
This is what the problem I had earlier was. The VM defaults to grabbing the guest tools from the WU server. So if you boot up the 1st time with this configuration, it will grab the Citrix tools 1st and you can't install the community tools.
Will the XCP-NG Windows PV Drivers fixed the network bottleneck issues? I have XenServer drivers installed and a 1Gb connection but only getting 100kbps speed from any of the windows VMs
@FPIT with PV tools, you should have 1Gbit network transfer rate, yes. This speed you have is more like the default emulated hardware.
@olivierlambert I have Xenserver PV drivers but it says they are from 2017 and I have a windows 10 computer hosting quickbooks and an employee is having terrible performance issues but we didnt have these performance issues with Hyper-V. Could it be related to the PV drivers being out of date?
Check in the device manager to see if all PV drivers are installed. Eg the network interface shouldn't be Realtek 8139 but Xen PV NIC or something like that.
Yea I did the windowsupdate checkbox in XO for the windows computers, but we still seem to have the same issues. I saw that broadcom NICs have performance problems with Xen and in general so that might be it. Im going to update the firmware and see and also add another network card to see if its the NICs in general. But im also gonna test the XCP-NG version windows drivers to see if they may be more compatible.
Please tell us about the NIC name in the device manager.
Well I just carved out a new server with Windows 2012 R2 on it to test running quickbooks to see if its maybe windows 10 thats being dumb like usual. But on the new server I am seeing XCP PV network device #0 and on the windows 10 one I was seeing XenServer PV network device #0
And both have identical network perfs?
Yes. I ran tests and everything seems perfectly fine until using quickbooks. Still having issues with Windows Server even. We are running some more scenarios to try to pin point the exact cause of the issue. Everything seems to run normal besides quickbooks. I wouldnt figure the network adapters would have anything to do with it if everything else seems to run fine.
I wanted to update the guest via https://github.com/xcp-ng/win-pv-drivers/releases (126.96.36.199);
Result, blue screen reboot ... Reign an old snapshot, I had to remove and put the VM on the field ....
So, I do not know how I am going to make this update of the guest tools, because yet the windows update was up to date ...
(They say that it is necessary to update WindowsUpdate before, it was good though ....; https://xcp-ng.org/forum/topic/1690/windows-10-1803-crash-with-installed-guest-tools I n did not have the same message and the same blue screen, but I still had that (on windows server 2016))
The option on XOA for Windows drivers is unchecked.
The language of windows server 2016 is in English (I tried on two servers with Snap happily ...).
VMs update by Windows update normally.
An idea for those who have succeeded?
Thank you very much in advance.
J'ai voulu mettre à jour les guest via https://github.com/xcp-ng/win-pv-drivers/releases (188.8.131.52);
Résultat, écran bleu au reboot... Reprit un ancien snapshot, j'ai du enlevé et remettre la VM sur le domaine....
Du coup, je ne sais pas comment je vais faire pour faire cette mise à jour des guest tools, car pourtant le windows update était à jour...
(Ils disent qu'il faut bien mettre à jour WindowsUpdate avant, il l'était bien pourtant.... ; https://xcp-ng.org/forum/topic/1690/windows-10-1803-crash-with-installed-guest-tools Je n'ai pas eu le même message et le même écran bleu, mais j'ai tout de même eu ça (Sur windows server 2016))
L'option sur XOA pour les drivers Windows est bien décochée.
La langue des windows server 2016 est en anglais (j'ai essayé sur deux serveurs avec du Snap heureusement...).
Les VMs se mettent à jour via Windows update normalement.
Une idée pour ceux ayant réussi ?
Merci beaucoup par avance.
@olivierlambert So I moved the quickbooks data files to my computer and hosted them and everything is working without any issues. My server has a Broadcom BCM7520 NIC in it. Could it be an issue with Broadcom NICs that could be causing this issue?
Oh yes. Broadcom NIC are shitty network cards. Take a look at
dmesgmaybe you'll see some errors there. Also check lost or error packets.
We have a more recent driver available in our test kernel: https://github.com/xcp-ng/xcp/wiki/Alternate-kernel