passthroughed pcie card crashs VM

Y

yamaharacer

Member
Jul 23, 2023
31
0
6
Hi there,
I have a problem with my macOS VM. It doesnt seem to be a macOS problem. It seems to be a passthrough problem.

Just prepared my VM with this manual:
https://computingforgeeks.com/how-to-run-macos-on-proxmox-ve/

After that I have updated every kext and the config.plist.

works very good. Then I have passthroued my RX570. Also works very good.

Now I want to passthrough my Fenvi T919 Wifi Card
hostpci1: 0000:08:00,pcie=1 and usb1: host=05ac:828d,usb3=1

early bind WIFI id 14e4:43a0 besides my id of an RX570: 1002:67df,1002:aaf0
vfio-config
Code: 
options vfio-pci ids=1002:67df,1002:aaf0,14e4:43a0 disable_vga=1
softdep nouveau pre: vfio-pci
softdep amdgpu pre: vfio-pci
softdep snd_hda_intel pre: vfio-pci


VM config:
Code: 
    args: -device isa-applesmc,osk="ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" -smbios type=2 -device usb-kbd,bus=ehci.0,port=2 -global nec-usb-xhci.msi=off -global ICH9-LPC.acpi-pci-hotplug-with-bridge-suppor>
    balloon: 0
    bios: ovmf
    boot: order=virtio0;net0
    cores: 4
    cpu: Penryn
    efidisk0: VM:100/vm-100-disk-0.qcow2,efitype=4m,size=528K
    hostpci0: 0000:02:00,pcie=1
    hostpci1: 0000:08:00,pcie=1
    machine: q35
    memory: 16384
    meta: creation-qemu=8.0.2,ctime=1699889619
    name: macOS
    net0: virtio=1E:AF:48:7C:0A:5E,bridge=vmbr0,firewall=1
    numa: 0
    ostype: other
    scsihw: virtio-scsi-pci
    smbios1: uuid=1a370df4-3387-4605-89e0-1221115ba86c
    sockets: 1
    usb0: host=1997:2433,usb3=1
    usb1: host=05ac:828d,usb3=1
    vga: none
    virtio0: VM:100/vm-100-disk-1.qcow2,cache=writeback,discard=on,iothread=1,size=120G
    vmgenid: c66306f2-199a-48c1-a077-124cf4735601


Then prepared the drivers with this manual and ran opencore legacy patcher.
https://www.hackintosh-forum.de/forum/thread/58656-anleitung-für-broadcom-wlan-patch-unter-macos-sonoma/

Works also good.

After activating the Wifi-> crash and reboot loop.

Its every time when I activate the Wifi card.

Could anybody help me? My opinion is, that I also have to guarantee that the host doesnt load the drivers, like with my AMD Card. But I dont know how the command is.

It seems that proxmox loads the host drivers:
dmesg | grep bcma
Code: 
[    1.011584] bcma-pci-bridge 0000:08:00.0: enabling device (0000 -> 0002)
[    1.011712] bcma-pci-bridge 0000:08:00.0: bus0: Found chip with id 0x4360, rev 0x03 and package 0x00
[    1.011738] bcma-pci-bridge 0000:08:00.0: bus0: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800, rev 0x2B, class 0x0)
[    1.011754] bcma-pci-bridge 0000:08:00.0: bus0: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812, rev 0x2A, class 0x0)
[    1.011780] bcma-pci-bridge 0000:08:00.0: bus0: Core 2 found: ARM CR4 (manuf 0x4BF, id 0x83E, rev 0x02, class 0x0)
[    1.011809] bcma-pci-bridge 0000:08:00.0: bus0: Core 3 found: PCIe Gen2 (manuf 0x4BF, id 0x83C, rev 0x01, class 0x0)
[    1.011823] bcma-pci-bridge 0000:08:00.0: bus0: Core 4 found: USB 2.0 Device (manuf 0x4BF, id 0x81A, rev 0x11, class 0x0)
[    1.048421] bcma-pci-bridge 0000:08:00.0: bus0: Bus registered
[   13.583646] b43: probe of bcma0:1 failed with error -95


I have already tryed softdep bcma pre: vfio-pci within vfio.config but after that, the VM also crashes and reboots in loop


syslog after starting the VM:
Code: 
Nov 15 13:34:42 proxmox pvedaemon[29729]: start VM 100: UPID:proxmox:00007421:000C3390:6554BAE2:qmstart:100:root@pam:
Nov 15 13:34:42 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: version 1.1
Nov 15 13:34:42 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: performing pre-reset
Nov 15 13:34:42 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: performing reset
Nov 15 13:34:42 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: CLOCK_CNTL: 0x0, PC: 0x28dc
Nov 15 13:34:42 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: performing post-reset
Nov 15 13:34:42 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: reset result = 0
Nov 15 13:34:42 proxmox systemd[1]: Started 100.scope.
Nov 15 13:34:43 proxmox kernel: device tap100i0 entered promiscuous mode
Nov 15 13:34:43 proxmox kernel: vmbr0: port 4(fwpr100p0) entered blocking state
Nov 15 13:34:43 proxmox kernel: vmbr0: port 4(fwpr100p0) entered disabled state
Nov 15 13:34:43 proxmox kernel: device fwpr100p0 entered promiscuous mode
Nov 15 13:34:43 proxmox kernel: vmbr0: port 4(fwpr100p0) entered blocking state
Nov 15 13:34:43 proxmox kernel: vmbr0: port 4(fwpr100p0) entered forwarding state
Nov 15 13:34:43 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Nov 15 13:34:43 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Nov 15 13:34:43 proxmox kernel: device fwln100i0 entered promiscuous mode
Nov 15 13:34:43 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Nov 15 13:34:43 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
Nov 15 13:34:43 proxmox kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Nov 15 13:34:43 proxmox kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Nov 15 13:34:43 proxmox kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Nov 15 13:34:43 proxmox kernel: fwbr100i0: port 2(tap100i0) entered forwarding state
Nov 15 13:34:44 proxmox kernel: vfio-pci 0000:02:00.0: enabling device (0400 -> 0403)
Nov 15 13:34:44 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: version 1.1
Nov 15 13:34:44 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: performing pre-reset
Nov 15 13:34:44 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: performing reset
Nov 15 13:34:44 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: CLOCK_CNTL: 0x0, PC: 0x28dc
Nov 15 13:34:44 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: performing post-reset
Nov 15 13:34:44 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: reset result = 0
Nov 15 13:34:44 proxmox kernel: vfio-pci 0000:02:00.0: vfio_ecap_init: hiding ecap 0x19@0x270
Nov 15 13:34:44 proxmox kernel: vfio-pci 0000:02:00.0: vfio_ecap_init: hiding ecap 0x1b@0x2d0
Nov 15 13:34:44 proxmox kernel: vfio-pci 0000:02:00.0: vfio_ecap_init: hiding ecap 0x1e@0x370
Nov 15 13:34:45 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: version 1.1
Nov 15 13:34:45 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: performing pre-reset
Nov 15 13:34:45 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: performing reset
Nov 15 13:34:45 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: CLOCK_CNTL: 0x0, PC: 0x2b58
Nov 15 13:34:45 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: performing post-reset
Nov 15 13:34:45 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: reset result = 0
Nov 15 13:34:45 proxmox systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status...
Nov 15 13:34:45 proxmox systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
Nov 15 13:34:45 proxmox systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill Switch Status.
Nov 15 13:34:45 proxmox pvedaemon[12285]: <root@pam> end task UPID:proxmox:00007421:000C3390:6554BAE2:qmstart:100:root@pam: OK
Nov 15 13:34:50 proxmox systemd[1]: systemd-rfkill.service: Deactivated successfully.
Nov 15 13:35:17 proxmox kernel: usb 1-13.3: reset full-speed USB device number 7 using xhci_hcd
Nov 15 13:35:17 proxmox kernel: usb 1-12: reset full-speed USB device number 3 using xhci_hcd
Nov 15 13:35:37 proxmox QEMU[29744]: kvm: vfio: Cannot reset device 0000:02:00.1, no available reset mechanism.
Nov 15 13:35:37 proxmox QEMU[29744]: kvm: vfio: Cannot reset device 0000:02:00.1, no available reset mechanism.
Nov 15 13:35:37 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: version 1.1
Nov 15 13:35:37 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: performing pre-reset
Nov 15 13:35:37 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: performing reset
Nov 15 13:35:37 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: CLOCK_CNTL: 0x0, PC: 0x24218
Nov 15 13:35:37 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: Performing BACO reset
Nov 15 13:35:37 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: performing post-reset
Nov 15 13:35:37 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: reset result = 0
Nov 15 13:35:41 proxmox kernel: usb 1-12: reset full-speed USB device number 3 using xhci_hcd
Nov 15 13:35:42 proxmox kernel: usb 1-13.3: reset full-speed USB device number 7 using xhci_hcd
Nov 15 13:37:14 proxmox pveproxy[22369]: worker exit
Nov 15 13:37:14 proxmox pveproxy[1324]: worker 22369 finished
Nov 15 13:37:14 proxmox pveproxy[1324]: starting 1 worker(s)
Nov 15 13:37:14 proxmox pveproxy[1324]: worker 30700 started
Nov 15 13:38:52 proxmox pveproxy[21205]: worker exit
Nov 15 13:38:52 proxmox pveproxy[1324]: worker 21205 finished
Nov 15 13:38:52 proxmox pveproxy[1324]: starting 1 worker(s)
Nov 15 13:38:52 proxmox pveproxy[1324]: worker 31240 started
Nov 15 13:40:45 proxmox QEMU[29744]: kvm: vfio: Cannot reset device 0000:02:00.1, no available reset mechanism.
Nov 15 13:40:45 proxmox QEMU[29744]: kvm: vfio: Cannot reset device 0000:02:00.1, no available reset mechanism.
Nov 15 13:40:45 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: version 1.1
Nov 15 13:40:45 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: performing pre-reset
Nov 15 13:40:45 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: performing reset
Nov 15 13:40:45 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: CLOCK_CNTL: 0x0, PC: 0x28e4
Nov 15 13:40:45 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: performing post-reset
Nov 15 13:40:45 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: reset result = 0
Nov 15 13:40:49 proxmox kernel: usb 1-12: reset full-speed USB device number 3 using xhci_hcd
Nov 15 13:40:49 proxmox kernel: usb 1-13.3: reset full-speed USB device number 7 using xhci_hcd
Nov 15 13:41:11 proxmox pvedaemon[12285]: <root@pam> successful auth for user 'root@pam'
Nov 15 13:41:15 proxmox pvedaemon[31944]: stop VM 100: UPID:proxmox:00007CC8:000CCD47:6554BC6B:qmstop:100:root@pam:
Nov 15 13:41:15 proxmox pvedaemon[14793]: <root@pam> starting task UPID:proxmox:00007CC8:000CCD47:6554BC6B:qmstop:100:root@pam:
Nov 15 13:41:15 proxmox kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Nov 15 13:41:15 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Nov 15 13:41:15 proxmox kernel: vmbr0: port 4(fwpr100p0) entered disabled state
Nov 15 13:41:15 proxmox kernel: device fwln100i0 left promiscuous mode
Nov 15 13:41:15 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Nov 15 13:41:15 proxmox kernel: device fwpr100p0 left promiscuous mode
Nov 15 13:41:15 proxmox kernel: vmbr0: port 4(fwpr100p0) entered disabled state
Nov 15 13:41:16 proxmox qmeventd[969]: read: Connection reset by peer
Nov 15 13:41:16 proxmox kernel: usb 1-13.3: reset full-speed USB device number 7 using xhci_hcd
Nov 15 13:41:16 proxmox pvedaemon[13836]: VM 100 qmp command failed - unable to open monitor socket
Nov 15 13:41:16 proxmox systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status...
Nov 15 13:41:16 proxmox systemd[1]: Reached target bluetooth.target - Bluetooth Support.
Nov 15 13:41:16 proxmox systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill Switch Status.
Nov 15 13:41:16 proxmox kernel: Bluetooth: hci0: BCM: chip id 73 build 1125
Nov 15 13:41:16 proxmox kernel: Bluetooth: hci0: BCM: product 05ac:828d
Nov 15 13:41:16 proxmox kernel: Bluetooth: hci0: BCM: features 0x07
Nov 15 13:41:16 proxmox kernel: Bluetooth: hci0: BCM20702B0 Generic USB Class 1 @ 20 MHz
Nov 15 13:41:16 proxmox kernel: usb 1-12: reset full-speed USB device number 3 using xhci_hcd
Nov 15 13:41:16 proxmox qmeventd[31960]: Starting cleanup for 100
Nov 15 13:41:16 proxmox qmeventd[31960]: trying to acquire lock...
Nov 15 13:41:16 proxmox kernel: input:   mini keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.0/0003:1997:2433.0009/input/input29
Nov 15 13:41:16 proxmox kernel: hid-generic 0003:1997:2433.0009: input,hidraw0: USB HID v1.01 Keyboard [  mini keyboard] on usb-0000:00:14.0-12/input0
Nov 15 13:41:16 proxmox kernel: input:   mini keyboard Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.1/0003:1997:2433.000A/input/input30
Nov 15 13:41:16 proxmox kernel: input:   mini keyboard System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.1/0003:1997:2433.000A/input/input31
Nov 15 13:41:16 proxmox kernel: input:   mini keyboard Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.1/0003:1997:2433.000A/input/input32
Nov 15 13:41:16 proxmox kernel: hid-generic 0003:1997:2433.000A: input,hidraw1: USB HID v1.01 Mouse [  mini keyboard] on usb-0000:00:14.0-12/input1
Nov 15 13:41:16 proxmox qmeventd[31960]:  OK
Nov 15 13:41:16 proxmox qmeventd[31960]: Finished cleanup for 100
Nov 15 13:41:16 proxmox pvedaemon[14793]: <root@pam> end task UPID:proxmox:00007CC8:000CCD47:6554BC6B:qmstop:100:root@pam: OK
Nov 15 13:41:16 proxmox systemd-logind[970]: Watching system buttons on /dev/input/event6 (  mini keyboard Consumer Control)
Nov 15 13:41:16 proxmox systemd-logind[970]: Watching system buttons on /dev/input/event3 (  mini keyboard)
Nov 15 13:41:16 proxmox systemd-logind[970]: Watching system buttons on /dev/input/event5 (  mini keyboard System Control)
Nov 15 13:41:16 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: version 1.1
Nov 15 13:41:16 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: performing pre-reset
Nov 15 13:41:16 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: performing reset
Nov 15 13:41:16 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: CLOCK_CNTL: 0x0, PC: 0x2c8c
Nov 15 13:41:16 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: performing post-reset
Nov 15 13:41:16 proxmox kernel: vfio-pci 0000:02:00.0: AMD_POLARIS10: reset result = 0
Nov 15 13:41:17 proxmox systemd[1]: 100.scope: Deactivated successfully.
Nov 15 13:41:17 proxmox systemd[1]: 100.scope: Consumed 7min 22.710s CPU time.
Nov 15 13:41:21 proxmox systemd[1]: systemd-rfkill.service: Deactivated successfully.
 
Last edited:
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom