Sebastian Scheinkman comments

Results 287 comments of


                                            Sebastian Scheinkman

use usespace vdpa can't find the pfName because the net path is wrong

but they are not VFs if I didn't miss anything from the logs you can see ``` I1123 02:59:05.269156 1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:00:0a.0 02 unknown unknown I1123...

use usespace vdpa can't find the pfName because the net path is wrong

these are the only selectors supported for devices that are not sriov PFs "pciAddresses" N Target device's pci address as string string list Default: null "pciAddresses": ["0000:03:02.0"] "acpiIndexes" N Target...

use usespace vdpa can't find the pfName because the net path is wrong

I don't understand also. @JasinlikeEatingOrange can you please explain what is this device as it doesn't look like a real PF

use usespace vdpa can't find the pfName because the net path is wrong

@JasinlikeEatingOrange base on > However, it's important to note that the code for simulating PF (Physical Function) and VF (Virtual Function) in the virtual environment is identical to that of...

use usespace vdpa can't find the pfName because the net path is wrong

ok so I think we are good to just use the rootDevices right?

use usespace vdpa can't find the pfName because the net path is wrong

closing this one

Fix can't get pfname for virtio pci path

/hold

Fix can't get pfname for virtio pci path

can I close this issue?

Add support for automatic bridge selection in HW offload mode

Hi @ykulazhenkov can you please rebase I would like to see the github actions green on this one

Add support for automatic bridge selection in HW offload mode

/retest