BeardElk

I'm gonna thank you for your advice, but ask that you don't respond to my posts anymore, as you're sounding more and more like a LLM with bad english, and don't even answer the questions I ask, you just ask me to do things a different way, just like a LLM. Can someone that has a vm with mac osx and working bluetooth and wifi please install hackintool and send me a screenshot of your pcie devices within osx/hackintool?

I've already confirmed that both the broadcom and intel card are detected and working with both linux and windows after driver install. The problem I have with mac is, if I leave it untouched after macinabox docker does it's thing, the card isn't detected in macos, regardless if I reset nvram or not. The only time it's detected is if i change the bus to 0x00 slot to 0x02 or 0x03 or 0x04, and if i set it to 0x03 I have to set the function to 0x01. But the kicker is, that when it's detected in macos, If I try to connect to wifi, i get that panic. My initial question was if someone could either point me to what an original mac/osx sets for its wifi card, or a working address. If I had a working mac I would install hackintools and just see what address the wifi card has, but I havent got a working one, and thats why I'm asking. I already know that osx is perticular about its addresses, as you have to set both the video and audio on the same slot for it to passthrough and work correctly. That's why I believe I simply have the wrong pcie address for the wifi to work.

panic-2025-02-03-215953.txtI'm getting this log in opencore.

Here's my full XML: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Ventura</name> <uuid>99ba95ae-5ba2-4f58-a691-3e642dcc6222</uuid> <metadata> <vmtemplate xmlns="unraid" icon="macinabox.png" os="osx" webui="" name="Linux"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='8'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='9'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='10'/> <vcpupin vcpu='6' cpuset='5'/> <vcpupin vcpu='7' cpuset='11'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-9.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/99ba95ae-5ba2-4f58-a691-3e642dcc6222_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' clusters='1' cores='4' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='hpet' present='no'/> <timer name='hypervclock' present='no'/> <timer name='pit' tickpolicy='delay'/> <timer name='rtc' tickpolicy='catchup'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback' discard='unmap'/> <source file='/mnt/user/domains2/Ventura/macos_disk.img'/> <target dev='hdc' bus='sata' rotation_rate='1'/> <serial>vdisk1</serial> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='9' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='9' port='0xc'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='10' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='10' port='0xd'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='11' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='11' port='0xe'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='ac:87:a3:2a:bc:52'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='2'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='sv' sharePolicy='ignore'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x05ac'/> <product id='0x8290'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <watchdog model='itco' action='reset'/> <memballoon model='none'/> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='************************'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-tablet'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd'/> <qemu:arg value='-cpu'/> <qemu:arg value='Skylake-Server,vendor=GenuineIntel,+hypervisor,+invtsc,kvm=on,+fma,+avx,+avx2,+aes,+ssse3,+sse4_2,+popcnt,+sse4a,+bmi1,+bmi2'/> </qemu:commandline> </domain>

Here's my first problem : " XML error: Attempted double use of PCI Address 0000:03:00.0 "

I'm wondering if someone could please help me with passing through either a wifi pcie bcm943602cs or built in AX210. I can't figure out what the correct address for the wifi card should be. OOTB neither works, and right now I'm on ventura trying to just figure out the bcm943602cs. I've tried OOTB, and <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/> (virtio-net has slot 0x03 func 0x0), and I've also tried slot 0x02 func 0x0, slot 0x04 func 0x0. I can get the card to show up, and I can see wifi networks in my area, but if I try to connect to one, the vm just hard reboots, and bluetooth has never worked with anything I've tried. Please! Someone help me!

I'm 99% sure its a docker container. During the last 40 minutes I've tried different ram combos and it still happens. The docker services starts up after a reboot, but that reboot has to be a hard reboot every time bc some freaking docker container wont shut down, so its stuck at "Retry unmounting disk share(s)..." and when I check, "status of dockerd: stopped", but its still in use. Excuse my language, but at this point, it feels like reinstalling every fucking docker from scratch is what I'll have to do. Any tips on figuring out which docker it is, other than starting one and see what happens. I'm gonna start by disabling those I rearly use, but I got a hunch that its gonna be plex or some fucker that's a nightmare to wipe clean and start from scratch, And I use daily.

I havn't had time to test anything yet, but my Docker Service failed to start again. syslog-192.168.1.111.log

I can't figure this one out on my own, and it feels like it just happens more and more frequently. Docker is running ipvlan, I've tried with and without "options i915 enable_dc=0" without any luck. First syslog starts on the 28 and ends today, the second part starts today and ends today. First part is with modprobe.d "options i915 enable_dc=0", second without. I've reinstalled nginx as well, in fact all my dockers, a couple of times, bc the docker service failed to start a bunch over the weekend, so I deleted the docker img and reinstalled all dockers from previous apps. When its working, everything is fine, and the next second it all becomes unresponsive and I have to force reboot the server, it doesn't even respond to ping. belk-diagnostics-20240930-1849.zip syslog-192.168.1.111 part 2.log syslog-192.168.1.111 part 1.log

I had a Samsung Fit 128gb usb drive on hand, and I didn't wanna risk getting any more data corruption bc of the usb drive disconnecting, so I plugged that in. Feels like its totally overkill but, if it works it works! The samsung fit was recommended as well.

Okay, so my USB drive just shat its fucking pants. Its deteriorating quckly. Anyone got a recommendation for a known Good usb drive??? Don't know if I just got a dud, but my it's a samsung drive thats failing.

For shits and giggles I changed usb port and I'm gonna see if it happens again. At least now I know what it is. I had it on an interal usb to "normal" usb adapter, just so it never gets unplugged by mistake, but I moved it to the back. Its all the same usb controller so I don't think it should make a difference, and I don't think the internal adapter just suddenly went bad, so the most likely culprit is the usb stick. But time will tell.

Thanks! It’s already in a usb 2.0 port, it’s been in that port since I built the server so the usb drive is probably going bad, gonna order a new one.

So for the last couple of months, my serves has randomly become unreachable on my local network, but all my dockers still work. So to try and find the problem I've had syslog running the last couple of weeks to catch whats happening when it happens, and 22:25 last night (january 28) it happened again. Now I don't have the skills to figure out what the errors are in the syslog, so I'm hoping someone on here can help me. I'm able to reboot the machine by using the onboard terminal, and when I do, it always failes to find the unraid USB stick, so I have to turn off my psu, wait 5-10 sec and then turn the machine on again for it to find the USB stick. Is my USB stick failing? Its a Samsung Bar Plus 32gb flash drive, not that old, might be coming up on 2-2,5 years, cant remember exactly when i bought it. Diag and Syslog attached. belk-diagnostics-20240129-1719.zip syslog-192.168.1.111.log

Thanks for your input, but I've decided to not continue forward with my timemachine setup as I already have a nextcloud thats working and it would only be a few apps that the timemachine would govern over.