bhyve iommu passthru ath0

[infoomatic]

fyi: I gave 13.0-RC4 a try, but this did not work out neither...


On 28.03.21 21:56, infoomatic wrote:
> Hi all,
>
> I own a pcengines apu2e4 where bhyve passthru is working in general.
> Passing through the i210AT NICs works fine. However, I bought a Compex
> WLE200NX a/b/g/n miniPCI card which is based on the Qualcomm Atheros
> AR9280 chip I also want to pass through.
>
> On the host I am running 12.2-RELEASE-p5.
>
> my loader.conf:
>
> hw.vmm.amdvi.enable=1
> vmm_load="YES"
> pptdevs="1/0/0 3/0/0 4/0/0"
> hw.vmm.iommu.enable=1
>
>
> pciconf -lv gives (relevant info; with igb0 used on the host):
>
> ppt0 at pci0:1:0:0:    class=0x028000 card=0x3099168c chip=0x002a168c
> rev=0x01 hdr=0x00
>     vendor     = 'Qualcomm Atheros'
>     device     = 'AR928X Wireless Network Adapter (PCI-Express)'
>     class      = network
> igb0 at pci0:2:0:0:    class=0x020000 card=0x00008086 chip=0x157b8086
> rev=0x03 hdr=0x00
>     vendor     = 'Intel Corporation'
>     device     = 'I210 Gigabit Network Connection'
>     class      = network
>     subclass   = ethernet
> ppt1 at pci0:3:0:0:    class=0x020000 card=0x00008086 chip=0x157b8086
> rev=0x03 hdr=0x00
>     vendor     = 'Intel Corporation'
>     device     = 'I210 Gigabit Network Connection'
>     class      = network
>     subclass   = ethernet
> ppt2 at pci0:4:0:0:    class=0x020000 card=0x00008086 chip=0x157b8086
> rev=0x03 hdr=0x00
>     vendor     = 'Intel Corporation'
>     device     = 'I210 Gigabit Network Connection'
>     class      = network
>     subclass   = ethernet
>
>
> in my vm-bhyve config I have
> passthru0="1/0/0"
> passthru1="4/0/0"
>
>
> which works nicely with the i210 adapter, but not with the wifi adapter.
> The wifi adapter also works when not passing through and using it via
> the host. In the VM (tried both the 12.2-RELEASE and 13.0-RC3), I have
> tried to load/unload various modules (or e.g. tried
> dev.ath.0.hal.force_full_reset=1), I do not get any connections, wifi
> scans/lists do not work. Other configurations result in "ath0: Device
> timeout" or in "wlan0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1".
>
>
> Any ideas how to resolve that?
>
>
> Regards,
>
> Robert
>
> _______________________________________________
> freebsd-virtualization at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe at freebsd.org"