future-address-23425
09/14/2022, 6:09 PMvfio-pci
driver through the Harvester configuration, using this:
os:
modules:
- vfio-pci
, with no luck. I made it work with:
os:
write_files:
- content: |
vfio-pci
path: /etc/modules-load.d/vfio-pci.conf
Any thoughts, am I missing sth? Shouldn't the first one work (do the same thing)?
I believe that vfio-pci
should be anyway enabled by default.limited-breakfast-50094
09/14/2022, 7:01 PMfuture-address-23425
09/14/2022, 7:10 PMkv/kubevirt
and how it triggers a controller update upon change of the driver of a PCI device (to/from vfio-pci
).3D controller
and thus excluded from your list. Also since the u-root
project doesn't use a PCI DB like https://pci-ids.ucw.cz/v2.2/pci.ids.gz, I would suggest filtering devices using their "PCI.Class" and not their "PCI.ClassName" which is not accurate (for example, https://pci-ids.ucw.cz/read/PD/12/00, which represents FPGA devices (mostly), is considered an unknown class id by the u-root
project).limited-breakfast-50094
09/15/2022, 9:52 PMfuture-address-23425
09/15/2022, 9:57 PMlimited-breakfast-50094
09/15/2022, 9:59 PMfuture-address-23425
09/15/2022, 10:00 PMlimited-breakfast-50094
09/15/2022, 10:03 PMClass
, it gives some weird results:
PCI Device: GP106 [GeForce GTX 1060 3GB]
Class: 196608
ClassName: DisplayVGA
Address: 0000:04:00.0
VendorId: 4318
DeviceId: 7170
ExtraInfo: []
lspci
, which is how I've been detecting the driverfuture-address-23425
09/15/2022, 10:09 PMpciutils
packages, you will find that pci.ids
DB under /usr/share/hwdata/
. There are libraries like jaypipes/pcidb
able to read it.limited-breakfast-50094
09/15/2022, 10:09 PMfuture-address-23425
09/15/2022, 10:13 PMlimited-breakfast-50094
09/15/2022, 10:14 PMfuture-address-23425
09/15/2022, 10:16 PMlimited-breakfast-50094
09/15/2022, 10:16 PMfuture-address-23425
09/15/2022, 10:21 PMlimited-breakfast-50094
09/15/2022, 10:22 PMvfio-pci
, and when I delete the PDC, I pop it back off and use the driver in use before that.future-address-23425
09/15/2022, 10:23 PMlimited-breakfast-50094
09/15/2022, 10:24 PMfuture-address-23425
09/15/2022, 10:24 PMlimited-breakfast-50094
09/15/2022, 10:26 PMfuture-address-23425
09/15/2022, 10:29 PMlimited-breakfast-50094
09/15/2022, 10:30 PMfuture-address-23425
09/15/2022, 10:31 PMlimited-breakfast-50094
09/15/2022, 10:32 PMvendorId:deviceId
pair, which is associated with a resourceName
, and then KubeVirt looks at the Node.Status.Allocatable for that resourceName
future-address-23425
09/15/2022, 10:38 PMlimited-breakfast-50094
09/15/2022, 10:40 PMyarn install
that dashboard repo I sent you, then API=$HARVESTER_MGMT_IP yarn dev
and it will spin up a server on port 8005future-address-23425
09/15/2022, 10:46 PMlimited-breakfast-50094
09/15/2022, 11:07 PMRANCHER_ENV=harvester API=192.168.1.147 yarn dev
That RANCHER_ENV=harvester has to be set nowfuture-address-23425
09/15/2022, 11:15 PMlimited-breakfast-50094
09/16/2022, 4:21 PMfuture-address-23425
09/16/2022, 9:20 PMresourceName
embedded in all this?limited-breakfast-50094
09/16/2022, 9:22 PMfuture-address-23425
09/16/2022, 9:24 PMresourceName
and you could use it to serve your own device plugin. I can help you with that. I could also help with the jaypipes/pcidb
migrations, but also modprobe/lsmod
migration to native Go code.limited-breakfast-50094
09/16/2022, 9:26 PMfuture-address-23425
09/16/2022, 9:27 PMlimited-breakfast-50094
09/16/2022, 9:32 PM