Good afternoon! My name is Ron and like most here I'm a Xenserver refugee. Love that this project exists and have already transitioned all my servers to XCP-ng. Can't wait to see where this project goes and will happily do what I can to see that it progresses.

R1 thank you thank you thank you I greatly appreciate your assistance! The driver worked and now I'm noticing a noticeable performance increase. I will continue to play around with it but so far so good!

Thank you very much again!

R1 thank you thank you thank you I greatly appreciate your assistance! The driver worked and now I'm noticing a noticeable performance increase. I will continue to play around with it but so far so good!

Thank you very much again!

Hii thanks again!

Within the source there is mention of an src.rpm file, but after searching I seem not to be able to find it. I will forward you the actual location for the non-rpm source: https://s3-us-west-1.amazonaws.com/aquantia-staging/wp-content/uploads/2018/06/Linux_2.0.10.0.zip .
It's an Aquantia AQC107 chipset. Asus, QNAP, and others use it. In fact this is how I came about having a few of these NIC cards; QNAP just came out with it and a very reasonable price, as well as a 10gbe copper switch. I've already got some ubuntu18.04lts servers running on it and it's quite stable so far (knock on wood).

Thank you so much again!

Ahhh I see. I was trying to follow the Citrix DDK instructions but it sort of went over my head, while within the source package there was a fast README document which I tried to follow as best as I could. There was a rpm method of compiling and storing, but I believe it also required source rpm and again I'm not very well versed in the Redhat/centos way of doing things, so I cheated :).

I guess I'll see if I can figure out how udev handles naming, as well as how to make the driver work (it "installs" but I notice that XCP-ng does not see it as operational).

Thanks again for the clues! I really appreciate it!

Hi! Thank you for the prompt response! I actually spent the night downloading the DDK VM, got it running, got the NIC card source code compiled, and transferred the *.ko modules to the server, as well as got it loaded into the kernel... At this point I'm battling two different fronts: 1. once module is loaded if i do an ifcondig -a the device shows up, but not in a traditional ethX. It states brside-876-eth2. I'm trying to figure out how Xenserver/XCP-ng interprets this (I know it's based on a recent version of Centos, but being that I am more of a debian guy I'm trying to figure out what it all means). 2. The management console considers it to be disconnected (i.e. not connected, even if it is and lit up). So yeah, lots of figuring out at this point. Sorry for the rambling, if you have any clue that can lead me to the right direction I'd appreciate it!

Thanks.

Good day everyone! Asking because right now using XCP-ng 7.4.1 which has kernel version 4.4.0+10. As of right now have on hand a few NIC cards with the AQC107 chipset (Nbase-T) which is supported natively by Linux Kernel starting with 4.4.11 (which means, of course, the current kernel does not support the card/chipset). Any help with info would be greatly appreciated.

Thank you very much again!

Good afternoon! My name is Ron and like most here I'm a Xenserver refugee. Love that this project exists and have already transitioned all my servers to XCP-ng. Can't wait to see where this project goes and will happily do what I can to see that it progresses.