Problems with Qualcomm Atheros QCNFA765

[sergiomuinhos]

Good evening,
I'm trying to allow my server to use the network card QCNFA765.
For later I'll use and connect it in Openwrt.
I am doing PCI Passthrough and just configured iommu.
The status is unknown, I don't know if I will have to install some extra drivers.
Not sure how, couldn't find any info on installing drivers.
Actualli if i do on Shell
Shows this:
06:00.0 Network controller: Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter (rev 01) Subsystem: Lenovo QCNFA765 Wireless Network Adapter Kernel driver in use: vfio-pci Kernel modules: ath11k_pci
The real problem start when i configure this card in a PCI Device in a LVM with OpenWrt.
It not works and show this in Openwrt:
kvm: -device vfio-pci,host=0000:06:00.0,id=hostpci0,bus=ich9-pcie-port-1,addr=0x0: vfio 0000:06:00.0: Failed to set up TRIGGER eventfd signaling for interrupt INTX-0: VFIO_DEVICE_SET_IRQS failure: No such device TASK ERROR: start failed: QEMU exited with code 1
In the Syslogs show this:
Aug 11 17:15:12 proxmox kernel: vmbr1: port 4(tap100i0) entered disabled state Aug 11 17:15:13 proxmox pvedaemon[85479]: start failed: QEMU exited with code 1 Aug 11 17:15:13 proxmox pvedaemon[39354]: <root@pam> end task UPID:proxmox:00014DE7:00066E45:64D6507A:qmstart:100:root@pam: start failed: QEMU exited with code 1 Aug 11 17:15:13 proxmox kernel: vfio-pci 0000:06:00.0: Unable to change power state from D3cold to D0, device inaccessible Aug 11 17:15:13 proxmox kernel: vfio-pci 0000:06:00.0: Unable to change power state from D3cold to D0, device inaccessible Aug 11 17:15:13 proxmox systemd[1]: Stopping user@0.service - User Manager for UID 0... Aug 11 17:15:13 proxmox systemd[85379]: Activating special unit exit.target... Aug 11 17:15:13 proxmox systemd[85379]: Stopped target default.target - Main User Target. Aug 11 17:15:13 proxmox systemd[85379]: Stopped target basic.target - Basic System. Aug 11 17:15:13 proxmox systemd[85379]: Stopped target paths.target - Paths. Aug 11 17:15:13 proxmox systemd[85379]: Stopped target sockets.target - Sockets. Aug 11 17:15:13 proxmox systemd[85379]: Stopped target timers.target - Timers. Aug 11 17:15:13 proxmox systemd[85379]: Closed dirmngr.socket - GnuPG network certificate management daemon. Aug 11 17:15:13 proxmox systemd[85379]: Closed gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers). Aug 11 17:15:13 proxmox systemd[85379]: Closed gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted). Aug 11 17:15:13 proxmox systemd[85379]: Closed gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation). Aug 11 17:15:13 proxmox systemd[85379]: Closed gpg-agent.socket - GnuPG cryptographic agent and passphrase cache. Aug 11 17:15:13 proxmox systemd[85379]: Removed slice app.slice - User Application Slice. Aug 11 17:15:13 proxmox systemd[85379]: Reached target shutdown.target - Shutdown. Aug 11 17:15:13 proxmox systemd[85379]: Finished systemd-exit.service - Exit the Session. Aug 11 17:15:13 proxmox systemd[85379]: Reached target exit.target - Exit the Session. Aug 11 17:15:13 proxmox systemd[1]: user@0.service: Deactivated successfully. Aug 11 17:15:13 proxmox systemd[1]: Stopped user@0.service - User Manager for UID 0. Aug 11 17:15:13 proxmox systemd[1]: Stopping user-runtime-dir@0.service - User Runtime Directory /run/user/0... Aug 11 17:15:13 proxmox systemd[1]: run-user-0.mount: Deactivated successfully. Aug 11 17:15:13 proxmox systemd[1]: user-runtime-dir@0.service: Deactivated successfully. Aug 11 17:15:13 proxmox systemd[1]: Stopped user-runtime-dir@0.service - User Runtime Directory /run/user/0. Aug 11 17:15:13 proxmox systemd[1]: Removed slice user-0.slice - User Slice of UID 0. Aug 11 17:15:15 proxmox kernel: pcieport 0000:00:1d.3: Data Link Layer Link Active not set in 1000 msec Aug 11 17:15:15 proxmox systemd[1]: 100.scope: Deactivated successfully.

It's not the card.
It is the PCI Passthrough that gives war.
Something related to PCIe power saving, to see if someone has faced the same (especially with GPUs or NICs) and something can be done

Any tip or solution? Thanks