Arvid E. Picciani

this appears to be required for macos. can we sponsor this?

made a new dts, this works for me ``` /dts-v1/; /plugin/; / { fragment@2 { target = ; __overlay__ { status = "okay"; fanctrl: emc2301@2f { reg = ; compatible...

just appening O_RDWR if its not a dir works, but i'm not sure if this is correct ```go case styx.Topen: s, err := os.Stat(p) if err != nil { continue...

this appears to be a timing issue. just waiting a second makes it work. i guess calling iproute2 cli just takes longer. is it possible that this needs link local...

> Have you considered statically linking, so there are no runtime dependencies on shared libraries? this seems unfeasible. it needs lvm2 which has a memory allocator that depends on being...

turns out its possible. https://gist.github.com/aep/ef25923766f4a1fedcc6c9ff09fa5079 but it's a giant PITA and adds GPL infections, so we'll probably instead contribute to this library.

attempted to work around it with a hook sidecar. i can add the xml to libvirt, but that doesnt help because its running inside a namespace, so its missing information...

i implemented my own device-plugin now that passes `/dev/vfio/123` into the pod and sets the `PCI_RESOURCE_` env to the pcie address. apparantly i'm missing something else tho. `unsupported configuration: host...

finally figured it out. the plugin is here: https://github.com/kraudcloud/vf-device-plugin but i dont think this can be upstreamed. in order to distinguish devices by path, i had to create a k8s...

thanks for the input. do you think i should prepare this for upstreaming into kubevirt ( pciPathSelector, create one resource per pcie path in config ) or would it be...