What kernel version will 7.5 have?
-
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.
-
Cool. Congratulations on getting most of it done!
AFAIK There are udev rules that make alien naming of ethernet devices to ethx, they run at boot time, so you need to figure out a way of loading the module at boot time such that once the udev rules run - you get your eth.
Instead of using .ko you can actually build an rpm - given time and interest - to make it package correctly.
-
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!
-
Point me to sources.. I'll bake an rpm and see if it works.
-
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!
-
@alphastarr128 I could compile the rpm from given sources.
See if it works. https://github.com/rushikeshjadhav/AQC107-XenServer
@olivierlambert Can this & such be moved to development category?
-
Moving the thread right now!
-
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!
-
Yay! good news!
We'll find a way to include this driver to be available in a repo
(pinging @stormi to think about the best solution to do so) -
Yes, we'll definitely create a RPM repository for community additions to the core XCP-ng. Ideally with an infrastructure efficient enough to allow you to post your packages to it without us being the only relay.
Like in most linux distros, in fact.Until this is ready, we can probably host a simple repository and upload the packages there ourselves.
-
-
@r1 Hi I am trying to get the AQC107 running under XenServer 7.1 which the kernel version is 4.4.0+2, but I do not have the DDK VM, can you help to create a RPM for it as well or let me know where can I get the DDK VM for 7.1? Thank you very much! Here is the source code of the driver "https://s3-us-west-2.amazonaws.com/aq-media/wp-content/uploads/2017/05/20181228_Linux_ver_2.0.22.071.zip"
-
XenServer 7.1? We are not providing any support for XenServer, or maybe I missed something in your question?
-
Actually just try to have the same driver for 4.4.0+2, thank you.
-
Oh I get it now
-
I still don't get the "ask"
