Issue with VM network dropping in and out

Andrew

@glenlewis09 I'll look at changing the default in the XCP r8125 driver until Realtek can fix it (which may be never).

glenlewis09

@Andrew @gskger @olivierlambert @john-c

Truly Thank you so much for helping me resolve this issue.

I know I have to run the command on each reboot, but it is much better than having hardware I can't even use.

To all that help me and walked me through the process thank you

I know you all have much on your plates but to take the time to dive into this problem is awesome!

If you do release an update to the driver let me know so I can test it. I owe you for the help!

Andrew

@glenlewis09 You can download an updated driver test from my page.

Just log in to the XCP host(s), use wget to download the RPM files and then use yum install r8125.... to install it and reboot.

olivierlambert

Darn crappy hardware, I'm not surprised but Realtek never disappoint

glenlewis09

@Andrew said in Issue with VM network dropping in and out:

yum install r8125

What URL should I use for the wget, I guess this allows me to add a repository for the yum update to download from?

I tried: wget https://xcp-ng.org which was just a random try.

But that was most definitely not the correct URL. I don't think the index page will help me much lol.

Again thanks for all the help on this.

gskger

@glenlewis09 There is a my page link in Andrews post?

glenlewis09

@gskger @Andrew

I will drink more coffee next time, I was excited and missed my page link.

Thank you again.

Mt_KEGan

@Andrew,

I realize this is an old topic, but found it to be VERY helpful and maybe it will be for someone else.

I decided to move to mini pcs (GMKTEC NucBox K6s) for my homelab/XCP-ng pool.

Although my RDP was pretty solid, and the VM behaved properly via my XOA interface, my network was CLEARLY not working with my Realtek 8125 NIC drivers while on 8.3. SMB transfers getting stuck (basically not working at all), and my pre-Xentools internet speed test was at ~200mbps download, while post Xentools I was only getting 2-7mbps (Xentools not XCP-ng pre-release guest tools). I'm sure an iperf test would've revealed the same problem with a local transfer as well. A problem no doubt! I found that the ethtool -K eth0 tx off tso off command corrected my issue but doesn't persist on the host. Bummer.

My interfaces basically matched the outputs already performed by the op.

My system is fully up to date and patched, yet the yum installer stated my r8125-module-9.012.04-1.xcpng8.3.x86_64 was "already installed and latest version" and I had "Nothing to do". Well this simply isn't correct for my use case!

I used Andrew's modified rpm package (notice the "-2" vs the "-1") in which he modified "with TXcsum/SG/TSO disabled by default. This fixes problems with Windows Server VMs an on-board RTL8125 chips".

Once I ran (as he suggested): wget https://users.ntplx.net/~andrew/xcp/r8125-module-9.012.04-2.xcpng8.3.x86_64.rpm & yum install r8125-module-9.012.04-2.xcpng8.3.x86_64.rpm my problems simply went away.

So I post this to help others (is it just me with this problem on the whole internet?), and pose the question to Vates: why is the updated installer not considered the most up to date package in your repo (in other words the ...-2 vs the ...-1)?

I can only assume that my issue (by using cheap mini pcs...which is MY fault of course!) is limited and the team doesn't want "TXcsum/SG/TSO disabled by default" for the masses using Realtek 8125 drivers. If that is the case, makes sense. I won't pretend to be smart enough to know the implications of doing that globally for all of 8.3.

Am I correct in assuming this? Is there something I'm missing?

Thank you @olivierlambert, Andrew, @gskger, and all others associated with the Vates team for helping the homelab community (smart because I also have a real enterprise I.T. sysadmin job and if left to me I'd use officially supported XCP-ng instead of cough hyper-v) and providing an open source product which is developed in a smart, planned way that works beautifully. Your contributions don't go unnoticed even though your community may have a problem or two every once in a while that we don't understand. ...Or bring upon ourselves

Andrew

@Mt_KEGan While my driver package uses the same name with an updated version, it is not an official XCP/Vates package. I have submitted an updated driver package to set the safer defaults. It's the same code with just different default settings.

Mt_KEGan

@Andrew thanks for all your hard work. I guess time will tell if the Vates team has to add those defaults to their official package or maybe I just got "lucky"