Multiple NICs on FeitCSI #2

Closed
opened 2024-10-25 15:17:25 +03:00 by cfalas · 1 comment
Owner

As far as I can see, FeitCSI only supports a single NIC at a time. In order to change this, I came up with the following two approaches:

  1. Set up virtual machines, with PCIe passthrough, such that each VM has FeitCSI installed and only sees a single NIC
  2. Patch FeitCSI such that it supports multiple NICs. This might be as simple as adding a few for loops for each physical device detected (since all NICs are already detected).

For example here

In both cases, some way to distinguish the NIC that sends the data will need to be added. In the first case, this might just be a different port number, but for the second case this will need to be added to the source code (e.g. an extra field in the CSI data).

As far as I can see, FeitCSI only supports a single NIC at a time. In order to change this, I came up with the following two approaches: 1. Set up virtual machines, with PCIe passthrough, such that each VM has FeitCSI installed and only sees a single NIC 2. Patch FeitCSI such that it supports multiple NICs. This might be as simple as adding a few for loops for each physical device detected (since all NICs are already detected). For example [here](https://github.com/KuskoSoft/FeitCSI/blob/7860485dbed5e4a2333b4a4ffae6287e15040cfb/src/WiFIController.cpp#L135) In both cases, some way to distinguish the NIC that sends the data will need to be added. In the first case, this might just be a different port number, but for the second case this will need to be added to the source code (e.g. an extra field in the CSI data).
cfalas added this to the Experimental setup project 2024-10-25 15:17:25 +03:00
Author
Owner

This has been done using the first option, i.e. running Proxmox on each machine, with PCIe passthrough, and having each VM boot off of iPXE

This has been done using the first option, i.e. running Proxmox on each machine, with PCIe passthrough, and having each VM boot off of iPXE
Sign in to join this conversation.
No Label
idea
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cfalas/dissertation#2
No description provided.