Topics created by WayneSherman

@dinhngtu said in Issues with XCP-ng Windows PV Tools 9.0.9000.0 Testsign Pre-release:

With 9.0.9000.0, you could sometimes run into this issue if you reboot too early after installing. This will also be fixed in the next release.

I just did two more tests and the boot-up failure happened both times. On the last test I waited some time (like 30 to 60 sec) after the driver installation before rebooting (using Windows restart from the start menu). Even though I waited before rebooting I still encountered the boot-up problem:

Windows is spinning on this screen and doesn't finish booting:
ef30a370-5897-41e6-a0f1-41fa3720dacb-image.png

I confirm this behavior. Checking with the dev team to see if this is by design.

I have been investigating a network hardware offload issue with the Realtek RTL8125BG 2.5G on the same XCP-ng host computer. This separate issue was resolved by shutting off TX checksum offload on the physical interface.

It made me think that maybe the mouse problem is caused by something similar on the other NIC. The second NIC in the computer is Realtek R8111EPV (1G)(using Linux r8169 driver) which is the one I have been using when I noticed the mouse issue. So I ran a capture test on the XCP-ng host:

tcpdump -i eth1 -v -nn | grep incorrect

and found bad packet checksums on some of the received packets coming in to the Windows VM:

x.x.x.x.443 > [windows.vm.ip].49715: Flags [P.], cksum 0xc656 (incorrect -> 0xb854), seq 1:2433, ack 216, win 2052, length 2432 x.x.x.x.443 > [windows.vm.ip].49717: Flags [P.], cksum 0x2e6c (incorrect -> 0xcff2), seq 1:2921, ack 218, win 501, length 2920 x.x.x.x.443 > [windows.vm.ip].49720: Flags [.], cksum 0x1b11 (incorrect -> 0xb99c), seq 1:2921, ack 213, win 16384, length 2920 ...

Running this on the XCP-ng host stopped the checksum errors:

ethtool -K eth1 gro off # testing only, not persistent

Making this setting persistent:

xe pif-param-set uuid=my_eth1_PIF_UUID other-config:ethtool-gro="off"

After making this change I will monitor the VM to see if the mouse problem returns.