4 hours ago, InfrastructureAdmin6969 said:

Hey Everyone, I have installed Sequoia and got to the desktop, but when I try and install a app from the app store and try and log in, I get "Verification Failed: Unknown Error Occurred". I saw a couple of replies similar but no definitive explanation as to how to fix this issue.  Things I have tried are switching the Network adapter to e1000.

See my messages above about installing the VMHide kext. It's needed to be able to authenticate with your Apple account.

Edited January 25, 20251 yr by Ancalagon

On 1/20/2025 at 3:45 AM, Ancalagon said:

Installing the VMHide kext resolves the issue with Apple accounts on macOS Sequoia. After installing the kext, I was able to click continue on the "Update Apple account settings" prompt and it succeeds.

^^^^This is golden - it fixed the issue for me on Sequioa. Thanks man!

@Ancalagon Thanks for the help! Got the VM up and running with Apple services. Any idea how to bypass the bootloader screen? I tried disabling the picker in opencore configurator but unfortunately now the VM won't boot.

10 hours ago, wewantrice said:

@Ancalagon Thanks for the help! Got the VM up and running with Apple services. Any idea how to bypass the bootloader screen? I tried disabling the picker in opencore configurator but unfortunately now the VM won't boot.

Set ShowPicker to false in your config.plist.

anyone else having problems with the keyboard key COMMAND when connecting through VNC from a mac(book) keyboard?

My CONTROL button works, OPTION too, but the COMMAND key is also mapped/recognized as the OPTION key. This makes it hard to perform simple tasks like copy/paste etc.

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!

 

Edited February 3, 20251 yr by BeardElk
Missed the -net on virtio-net. / added screenshot.

33 minutes ago, BeardElk said:

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!

 

Your VFIO looks good. 
lspci -v should show vfio-pci driver in use for the [14e4:43ba] broadcom device..

so lets review the xml of the vm for ventural:

<hostdev mode='subsystem' type='pci' managed='yes'>
  <source>
    <address domain='0x0000' bus='0xXX' slot='0xXX' function='0xX'/>
  </source>
  <rom bar='off' file='/mnt/user/domains/bios_folder/network_rom.rom'/>
  <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
</hostdev>

*Replace the address values (bus, slot, function) with those of your PCI device, which you can find under System Devices in Unraid.

<address domain='0x0000' bus='0xXX' slot='0xXX' function='0xX'/>
needs the data edited to point to your PCIe card...

once the xml is corect in passing the pcie card. we need to boot to the os and check kext drivers:
macOS Driver (Kext) Setup:
*--macOS detects the device (About This Mac > System Report > PCI)
Double Chekc The correct driver (kext) is loaded. You can check loaded kexts using:
 

kextstat | grep -i broadcom

^-Apple Terminal Command...
*- If it doesn’t show up, try resetting NVRAM in the macOS recovery menu to refresh device detection.

 

--

If there are issues:

Install AirportBrcmFixup.kext and Lilu.kext via OpenCore if necessary.

Make sure OpenCore config (config.plist) doesn’t block BCM wireless hardware

 

Other checks:
 

Potential Issues and Solutions

Device ID Mismatch:
Even though macOS Ventura supports the card, the passed-through PCI device may require a compatible device ID to work correctly. Use a kext patch (e.g., via config.plist patching) if needed.

 

ROM File Requirement:
Some devices may need a ROM file passed with the device to initialize correctly. You can dump your device’s ROM on a Linux machine using rom-parser.

 

VT-d/IOMMU:
Ensure IOMMU (VT-d for Intel or AMD equivalent) is enabled in your BIOS.

 

Error Logs:
Check logs in macOS with Console.app for any PCI or hardware errors.

10 minutes ago, bmartino1 said:

Your VFIO looks good. 
lspci -v should show vfio-pci driver in use for the [14e4:43ba] broadcom device..

so lets review the xml of the vm for ventural:

<hostdev mode='subsystem' type='pci' managed='yes'>
  <source>
    <address domain='0x0000' bus='0xXX' slot='0xXX' function='0xX'/>
  </source>
  <rom bar='off' file='/mnt/user/domains/bios_folder/network_rom.rom'/>
  <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
</hostdev>

*Replace the address values (bus, slot, function) with those of your PCI device, which you can find under System Devices in Unraid.

<address domain='0x0000' bus='0xXX' slot='0xXX' function='0xX'/>
needs the data edited to point to your PCIe card...

once the xml is corect in passing the pcie card. we need to boot to the os and check kext drivers:
macOS Driver (Kext) Setup:
*--macOS detects the device (About This Mac > System Report > PCI)
Double Chekc The correct driver (kext) is loaded. You can check loaded kexts using:
 

kextstat | grep -i broadcom

^-Apple Terminal Command...
*- If it doesn’t show up, try resetting NVRAM in the macOS recovery menu to refresh device detection.

 

--

If there are issues:

Install AirportBrcmFixup.kext and Lilu.kext via OpenCore if necessary.

Make sure OpenCore config (config.plist) doesn’t block BCM wireless hardware

 

Other checks:
 

Potential Issues and Solutions

Device ID Mismatch:
Even though macOS Ventura supports the card, the passed-through PCI device may require a compatible device ID to work correctly. Use a kext patch (e.g., via config.plist patching) if needed.

 

ROM File Requirement:
Some devices may need a ROM file passed with the device to initialize correctly. You can dump your device’s ROM on a Linux machine using rom-parser.

 

VT-d/IOMMU:
Ensure IOMMU (VT-d for Intel or AMD equivalent) is enabled in your BIOS.

 

Error Logs:
Check logs in macOS with Console.app for any PCI or hardware errors.

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

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>

 

Edited February 3, 20251 yr by BeardElk
Had wrong bus/slot/func

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

Nothing I can do if its panics... nvram reset and doublecheck your opencore boot stuff... Its easy to "hose" theses...

I don't see the pcie device in the xml code... 
I don't have the data to grab the device for the buss, etc..etc...

I have to assume if you did add it it is this xml code:
 

<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='0x02' slot='0x00' function='0x0'/>
</hostdev>

...BUT!

The IOMMU group for the Broadcom device in your image shows 0b:00.0 with PCI vendor ID 14e4:43ba.

The current XML's <hostdev> section uses bus='0x0b' slot='0x00' function='0x0', which matches the IOMMU group location (0b:00.0). However, it may not be set up fully or correctly detected by macOS...

But that doesn't seem correct and may be a different device... there should be an option at the bottom of the gui side to add the device. Then you will need to rerun macos docker to fix the xml due to unraid changes...

Per other posts...
The Here's my first problem : " XML error: Attempted double use of PCI Address 0000:03:00.0 "

Means that we can't use <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
as its already in use else where... or you flat added the host dev and didn't change the bus etc to point to your Broadcom device... not enoth info ... or that is the corect xml but you need to remove it and only use it once...

Id recomend testing the vfio and the device in a differenet linux vm or widnows vm and pass it via unraids vm xml first then copy paste the deivice from that vms xml into the apple xml...

you may need to reset the nvram and rerun the macos docker to fix things...
 

19 minutes ago, bmartino1 said:

Nothing I can do if its panics... nvram reset and doublecheck your opencore boot stuff... Its easy to "hose" theses...

I don't see the pcie device in the xml code... 
I don't have the data to grab the device for the buss, etc..etc...

I have to assume if you did add it it is this xml code:
 

<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='0x02' slot='0x00' function='0x0'/>
</hostdev>

...BUT!

The IOMMU group for the Broadcom device in your image shows 0b:00.0 with PCI vendor ID 14e4:43ba.

The current XML's <hostdev> section uses bus='0x0b' slot='0x00' function='0x0', which matches the IOMMU group location (0b:00.0). However, it may not be set up fully or correctly detected by macOS...

But that doesn't seem correct and may be a different device... there should be an option at the bottom of the gui side to add the device. Then you will need to rerun macos docker to fix the xml due to unraid changes...

Per other posts...
The Here's my first problem : " XML error: Attempted double use of PCI Address 0000:03:00.0 "

Means that we can't use <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
as its already in use else where... or you flat added the host dev and didn't change the bus etc to point to your Broadcom device... not enoth info ... or that is the corect xml but you need to remove it and only use it once...

Id recomend testing the vfio and the device in a differenet linux vm or widnows vm and pass it via unraids vm xml first then copy paste the deivice from that vms xml into the apple xml...

you may need to reset the nvram and rerun the macos docker to fix things...
 

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.

Edited February 3, 20251 yr by BeardElk
Spelling

5 minutes ago, BeardElk said:

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.

unlease the card has that funciton it should be set and you need function 0 and funtion 1 to be passed simlar to the gpu passthorugh. as your spliting the card in hav at 2 different bus. I usualy turn back to hackintosh stuff to opencore install my self as seen earlier links on the forum of check adn dos over don't.

with vm you make the custm bus and slots but if your spliting and only pasing a part of the card then its dead at boot.

get it back into the state with mac os destop and teh device is there but don't try to use the card yet as I don't belvie the open core that is pre packaged has teh driver and settings open as orginal posted you need to edit the opencore plist file to confirm and allow its use...

you may even need to fake the pci id to make it work but taht pre os enviroment...
so make your own with https://dortania.github.io/OpenCore-Legacy-Patcher/

review:

as it applies to all and any pcie device! its doen't matter what apple things the pcie is as long as it s passed the other ids are generated at the kext level...

Apple is fickle with these cards make sure its on the compatible lists:
https://www.tonymacx86.com/threads/attempting-to-hack-macos-ventura-and-sonoma-to-support-broadcom-wi-fi-6-cards.327439/
 

16 minutes ago, bmartino1 said:

unlease the card has that funciton it should be set and you need function 0 and funtion 1 to be passed simlar to the gpu passthorugh. as your spliting the card in hav at 2 different bus. I usualy turn back to hackintosh stuff to opencore install my self as seen earlier links on the forum of check adn dos over don't.

with vm you make the custm bus and slots but if your spliting and only pasing a part of the card then its dead at boot.

get it back into the state with mac os destop and teh device is there but don't try to use the card yet as I don't belvie the open core that is pre packaged has teh driver and settings open as orginal posted you need to edit the opencore plist file to confirm and allow its use...

you may even need to fake the pci id to make it work but taht pre os enviroment...
so make your own with https://dortania.github.io/OpenCore-Legacy-Patcher/

review:

as it applies to all and any pcie device! its doen't matter what apple things the pcie is as long as it s passed the other ids are generated at the kext level...

Apple is fickle with these cards make sure its on the compatible lists:
https://www.tonymacx86.com/threads/attempting-to-hack-macos-ventura-and-sonoma-to-support-broadcom-wi-fi-6-cards.327439/
 

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?

Edited February 3, 20251 yr by BeardElk

On 1/28/2025 at 4:14 AM, RezzZ said:

anyone else having problems with the keyboard key COMMAND when connecting through VNC from a mac(book) keyboard?

My CONTROL button works, OPTION too, but the COMMAND key is also mapped/recognized as the OPTION key. This makes it hard to perform simple tasks like copy/paste etc.

this has to do with the sig terms generated with the VM and passing a keybaord. example a windows keyboard sith the super key is a different signal term dependant on the OS. You need to re alocate your apples keybaord vai the settings in its localazation and lanuage....

settings > Keyboard > Modifier Keys

https://support.apple.com/en-bn/guide/mac-help/mchl84525d76/mac

https://apple.stackexchange.com/questions/437984/option-and-command-key-are-switched-for-a-keyboard-on-my-mac

Hi, I'm setting up passthru for my iGPU (Intel i5  Alderlake) - Unraid V7.0.0 - MacOS Sonoma

 

To do this I checked the GPU under Tools/Systen Devices, rebooted Unraid, and added the iGPU as 2nd GPU in the template

 

I can see the device under System Information/Graphics Displays, but it does not appear to be used. Under the device details it says "No Kext Loaded".  (See attached)  Compared to my how my physical Intel Mac Mini reports its iGPU, it looks quite different

 

Has anyone done this successfully? Do I need a kext? Or do I need to fix something in the XML?

 

Here's the part that looks relevant:

 

    </input>
    <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us' 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'/>
      <alias name='video0'/>
      <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='0x00' slot='0x02' function='0x0'/>
      </source>
      <alias name='hostdev0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
    </hostdev>
    <watchdog model='itco' action='reset'>
      <alias name='watchdog0'/>
    </watchdog>
    <memballoon model='none'/>
  </devices>

 

 

Thanks!

On 1/23/2025 at 5:20 AM, iamtim2 said:

I've been playing around with passthrough again in Unraid (V7.0.0) and finally got my GPU (rx580) and a PCIe USB controller passed through and working.

 

My system is an Intel Xeon, this 'fix' may not work for everyone and I've not done enough testing to see if it can be refined at all with some of the arguments used:

 

1.  Click on Main tab then the flash drive and replace the line that reads ‘append initrd=/bzroot’ under the UnraidOS box in the syslinux configuration with the following:

          

append video=vesafb:off,efifb:off initcall_blacklist=sysfb_init default initrd=/bzroot

 

2.  Install MacOS using Macinabox as per video/instructions and configure as required. Mine was already installed and working under VNC. As I'm on intel, I'm using CPU host passthrough passthrough arguments in the Macinabox docker configuration.

 

3.  Stub GPU and any other passthrough devices (Tools/System devices) and reboot

 

4.  Edit VM config and add GPU and PCI cards as required.

 

5.  Start Macinabox docker to correct XML

 

6.  Go back and edit VM, switch to form view and locate the following line:

 

<type arch='x86_64' machine='pc-q35-9.1'>hvm</type>

Replace machine type q35-9.1 with q35-6.0

 

7.  Save but do not start macinabox docker again otherwise it will revert the machine type to 9.1

 

8.  Boot VM and hopefully you get video passthrough.

 

Having passthrough issues too. Unfortunately your solution did not work for me.

 

I managed to launch the VM using VNC and turned on verbose booting to see what is happening. I suggest to turn on verbose booting to see the last message it gives on freeze. Instead of looking at the apple logo. You can do this by adding

-v to the boot args.

 

I'm stuck at "IOPCI Configurator: configure kIOPCIEnumerationWaitTime is 900"

 

Based on google results I got, I tried 2 things.

 

1) Turn off Resizeable Bar and Above 4G decode in BIOS. Did not help.

2) Use AppleMCEReporterDisabler.kext. Already was present in the install and updating it did not work either.

 

So here I am scratching my head. This used to be a fully working configuration. Considering downgrading to 6.12.x.

My MB bios is wonky admittedly so I'm doubting if the BAR settings are actually registering but I also did a bios update and reset the bios to default multiple times so, a very low possibility of that happening. If you are having an issue with the gpu passthrough maybe try disabling the Resizeable Bar.

 

If any of you kind folk have any ideas or pointers for my case, it would be amazing. Thanks.

 

UPDATE #1 - Rolled back to 6.12.10. It booted with GPU on q35 - 6.0 BUT it refuses to register my pcie usb card (FL1100). Will try more later and keep this updated.

 

UPDATE #2 - SUCCESS! Jumped from 1 bug to another, I finally managed to have a fully working GPU passthrough macOS Sonoma. I lost quite a bit of time dealing with the XML to be honest. I stopped getting any video output and my solution for that was to set the virtual bus for the GPU and the Audio to 02. (Obviously function to 0x01 per spaceinvader1's advanced GPU passthrough video). It automatically assigned it 05 and it was 05, it simply did not give any video output. For few times, multifunction and the function fixes on the xml editor did not stick either. I would hit apply and then go back to see it reverted. 

 

For the USB PCI card issues, I updated to 6.12.13 to see if it would help and it did help. Also since q35-6.0 is the highest I can go without having GPU passthrough issues, I fixed the xml only manually as that seems to be the only way to keep the machine type to q35-6.0.

 

Since I kind of need a working macOS, I will hold on updating to Unraid 7 until things are more stable. 

 

 

 

Edited February 10, 20251 yr by EG-Thundy

Hi, I'm trying to get a simple macOS VM setup to do testing for websites on Safari. Nothing strenuous. I have Unraid 7, I've installed the latest MacInABox, followed SpaceInvaderOne's video tutorial, but it stops at the white mac logo after selecting the Host icon and pressing enter. It never gets past the logo.

 

I have a dual Xeon CPU, 128 GB of system memory and a GPU, but at the moment I don't need to pass the GPU through (due to what I need for now).

 

When it launches, I get a bunch of this error message:

qemu-system-x86_64: warning: host doesn't support requested feature:

 

And when I try to shut off the VM, it won't shut off unless I go to Settings→VMS and turn it off and back on again.

 

Can anyone provide any pointers or suggestions to help me figure this out?

 

Thanks so much.

Hi all,

 

is there a recommended minimum for the primary vdisk for macos?

How do you manage userdata? Ideally I would like to store data directly on an unraid share, is that practical?

 

Thank you and kind regards,

SnakeZZ

I was able to set up the VM and get in without much trouble.  However, when I am in the VM I have no network access.  I find that odd as it was working when installing.  During the install it made me verify my icloud account and things were sent to my cell phone to verify the account, so it was working during setup?

 

Any suggestions?

Decided to try this out.  When running the container and choosing Senoma, I got the following error "Image verification failed".  The script kept running and I got the notification the VM was ready.  Is it??

 

Choose a product to download (1-8): Downloading 696-08090...
Saving http://oscdn.apple.com/content/downloads/11/58/062-53943/of12aseueo2jnehp03qh5g3o17lx4139t1/RecoveryImage/BaseSystem.chunklist to ./BaseSystem.chunklist...
0.0/0.0 MB |==========================| 100.0% downloaded                       
Download complete!
Saving http://oscdn.apple.com/content/downloads/11/58/062-53943/of12aseueo2jnehp03qh5g3o17lx4139t1/RecoveryImage/BaseSystem.dmg to ./BaseSystem.dmg...
753.0/753.0 MB |==========================| 100.0% downloaded                   
Download complete!
Verifying image with chunklist...
Image verification failed. ([Errno 25] Inappropriate ioctl for device)
mkdir: created directory '/domains/Sonoma'
I have created the Macinabox directories
.
Formatting '/domains/Sonoma/macos_disk.img', fmt=raw size=107374182400
.
Created vdisk

 

BTW, Unraid 7.0.1

 

Edited February 28, 20251 yr by ggee

I cannot seem to connect to the recovery server for any of the os versions. I followed the online tutorial and made sure I tried multiple nic settings. rerunning the docer after every change / attempt.

59 minutes ago, blackbox said:

I cannot seem to connect to the recovery server for any of the os versions. I followed the online tutorial and made sure I tried multiple nic settings. rerunning the docer after every change / attempt.

I am not sure if this is a me issue or a apple server issue.

So I am running 7.10 RC-1.

 

When trying to use Macinabox, I get an error message about the Profile.  How do I get this to work?

 

I believe I have correctly followed the instructions in the message, but I keep getting the same message.

 

Thanks!

 

I got it working, but I did two things.  Don't know which fixed it.  First I deleted a file that said delete me v4.

Then I deleted the template in VM create.

I shoudn't rush through.