ghost82

Do you have HDAU in ioreg beside the GPU? AppleALC correctly handles the audio (including that integrated in the gpu), so I think you need it. How do you currently manage the audio?

Here another issue, maybe related to the lack of c and p states: On real machintosh the output shows values for CPU_Scheduler_Limit, CPU_Available_CPUs and CPU_Speed_Limit. Lack of this may be linked to Turbo, and it can explain lower results in geekbench tests. Tried with different smbios: imacpro1,1 and also imac12,2 (because I have Sandy bridge). I tried: 1- Pike's script to generate SSDT: ./ssdtPRGen.sh -b Mac-7BA5B2D9E42DDD94 -p 'E5-2687W' By inserting the SSDT into opencore I see no relevant changes in ioreg. 2- CPUFriend + CPUFriendDataProvider ./ResourceConverter.sh --kext /System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/X86PlatformPlugin.kext/Contents/Resources/Mac-942B59F58194171B.plist CPUFriendDataProvider is generated, injected through opencore with lilu+CPUFriend, I can see in ioreg a new entry in AppleACPICPU named "cf-frequency-data", but no pstates nor cstates under X86PlatformPlugin. 3- Pike's script + CPUFriend + CPUFriendDataProvider Using Pike's script to generate SSDT (SSDT-pr.aml), then using it with ResourceConverter: ./ResourceConverter.sh --kext /Users/daniele/Desktop/SSDT-pr.aml CPUFriendDataProvider is generated (different from that of point 2), injected through opencore with lilu+CPUFriend, I can see in ioreg a new entry in AppleACPICPU named "cf-frequency-data", but no pstates nor cstates under X86PlatformPlugin. Also opencore during boot shows messages like "ACST and _CST evaluations failed", "APSS and _PSS evaluations failed", "Failed to get CPU P States", "Deepsleep is not supported". Ideas are ended

My audio is perfectly fine; I'm currently using lilu+appleALC but was working the same with voodooHDA. I'm passing through both nvidia and onboard audio: here is the relevant part of the xml: Nvidia gpu+audio (same bus, same slot, different function): <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x83' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/GTXTitanBlack.dump'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x83' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </hostdev> Onboard audio (bus 0): <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </hostdev>

Yes, mine is showing correctly. My xml config is similar to yours, with host-passthrough, exept that I'm also passing explicitly features: <qemu:arg value='host,+hypervisor,migratable=no,-erms,+invtsc,kvm=on,+topoext,+invtsc,+avx,+aes,+xsave,+xsaveopt,+ssse3,+sse4_2,+popcnt,+arat,+pclmuldq,+pdpe1gb,+rdtscp,+vme,+umip,check'/> You can try the following: - if you're using clover, input the cpu data: as an example, I'm reporting the data related to E5-2687W (see also cpu-z screenshot example): Frequency MHz: 3100 Bus Speed kHz: 105990 (mine was 100333) QPI: 3391 (mine was 4014) TDP: 150 These data reflect that appearing in cpu-z screenshot: in my case, when I was using clover, they were sligtly different, so it should be better to run cpu-z on your hardware and input these values. -if you're using opencore you can try to add custom-arg busratio, in my case for E5-2687W it's busratio=31. Also, you can add data into PlatformInfo->DataHub->ARTFrequency, FSBFrequency

Edited: wrong assumption

Same here. EDIT: To enable it, add to qemu arg migratable=no <qemu:arg value='host,migratable=no,+invtsc, From qemu wiki: New "invtsc" (Invariant TSC) CPU feature. When enabled, this will block migration and savevm, so it is not enabled by default on any CPU model. To enable invtsc, the migratable=no flag (supported only by -cpu host, by now) is required. So, invtsc is available only if using: -cpu host,migratable=no,+invtsc.

Add this patch in opencore if kernel panic is related to x86_validate_topology: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Kernel</key> <dict> <key>Patch</key> <array> <dict> <key>Comment</key> <string>Disable x86_validate_topology</string> <key>Count</key> <integer>0</integer> <key>Enabled</key> <true/> <key>Find</key> <data> 6PT1//+c </data> <key>Identifier</key> <string>kernel</string> <key>Limit</key> <integer>0</integer> <key>Replace</key> <data> Dx9EAACc </data> <key>Skip</key> <integer>0</integer> </dict> </array> </dict> </dict> </plist>

What about c and p-states? I'm not sure it is working properly, rather I think there's something broken (actually I'm not sure if states can be controlled in the guest).. In ioreg I don't have any value for c and p-states: Also, from mac os terminal, command: sudo powermetrics returns: Core 0 C-state residency: 0.00% (C3: 0.00% C6: 0.00% C7: 0.00% ) Core 1 C-state residency: 0.00% (C3: 0.00% C6: 0.00% C7: 0.00% ) ...... for all the cores. I'm using cpufriend kext + cpufrienddataprovider kext: cpufrienddataprovider kext was generated with ResourceConverter by feeding to it the ssdt generated with Pike's script (for cpu E5-2687W). Emulated cpu is Ivy Bridge. Data seem to be correctly injected: What about your values?

In clover go to kernel and kext patches --> KernelToPatch This wasn't working for me in clover, no problems in opencore. However, if I understood well and if your read the posts above, you will be able to set topology in xml, but you won't be able to make mac os recognize the correct topology; Penryn is the only cpu that works with topology. I don't think your problems are related to topology, maybe related to power management.

Ok, thank you, just to make sure I'm in the same boat as all of you I'm not a great guru, but I will try to understand what's happening.

Finally, by applying the patch in opencore mac os boots successfully and I can apply topology in the xml of the vm. However, mac os system profiler shows 16 cores/16 processors.. Without the patch there's a kernel panic related to x86_validate_topology, so the patch works, but for some reasons this does not make any difference in mac os. PS: shouldn't be not needed this patch in opencore after @Leoyzen commit to github? Latest compiled developer opencore is not able to boot without this kernel patch for me.

Ok, here is what I found: I was thinking the hfs+ driver was not needed as I'm running Catalina on apfs, but to boot recovery you need hfs driver. 1) VBoxHfs.efi (latest developer version compiled by me at the time of writing) is very slow, it took 3 minutes to boot the recovery, and it works only if in opencore there are ProvideCustomSlide=true and EnableSafeModeSlide=true (without these I have memory allocating 0xa00 type 2 error to boot into recovery). 2) Replacing VBoxHfs.efi with older HFSPlus.efi makes the boot into recovery faster (istantaneous), without the need of ProvideCustomSlide=true. 3) Latest ApfsDriverLoader.efi and AppleImageLoader.efi (latest developer version compiled by me at the time of writing) do not show any drive: I'm using apfs.efi from Catalina. 4) Latest UsbKbDxe.efi (latest developer version compiled by me at the time of writing) doesn't work: opencore hangs at tiano core logo.

Finally, I switched from clover to opencore 0.5.2, as it seems it will be the bootloader of the future with more development. I started from the qcow2 posted by @Leoyzen I noticed faster boot and all is working quite good, and finally I'm able to load x86platformplugin (however, I have problems with loading p and c states, has anybody been able to properly inject c and p-states?) instead of acpi_smc_platformplugin. Moreover I have also AGPM and AppleLPC, so for me it's better than clover. I have a problem related to boot into recovery; at the boot screen I have 2 options: 1 to boot into mac os, 2 to boot into recovery. If I choose 2, the vm freeze (I can monitor from unraid webui that one cpu is going to 100%): AvoidHighAlloc doesn't solve the problem. Maybe related to this: https://github.com/acidanthera/bugtracker/issues/389 But not solved for me. EDIT: I suspect the problem is in the apfs driver, here my tests: apfs.efi (from original catalina): able to boot mac os, not able to boot recovery (dmg) ApfsDriverLoader.efi (from AppleSupport package v. 2.1.2): drives not seen, no mac os, no recovery EDIT2: ApfsDriverLoader.efi from AppleSupport package 2.0.2 combined with AppleImageLoader.efi from AppleSupport package 2.0.2 is able to list both mac os and recovery drives. They are able to load mac os, not the recovery; when booting mac os it says AppleImageLoader is not AppleEfiFat, but it is able to load mac os. Definetely a driver problem. PS: newer version of ApfsDriverLoader.efi includes AppleImageLoader, but it doesn't work at all. Another thing I can't get to work is (apparently) kexts injection for drives different than the primary mac os: if I try to boot from a usb I have no signal to the monitor and this make me think that lilu+weg are not injected properly; however for primary mac os partition they are injected, since I have no additional patches for video. EDIT: maybe related to problem 1 Does your recovery work? Here is my opencore config if it needs: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>ACPI</key> <dict> <key>Add</key> <array> <dict> <key>Comment</key> <string>CPUS</string> <key>Enabled</key> <true/> <key>Path</key> <string>custom/SSDT-cpu.aml</string> </dict> <dict> <key>Comment</key> <string>EC and USBX injections</string> <key>Enabled</key> <true/> <key>Path</key> <string>custom/SSDT-EC-USBX.aml</string> </dict> </array> <key>Quirks</key> <dict> <key>FadtEnableReset</key> <false/> <key>NormalizeHeaders</key> <false/> <key>RebaseRegions</key> <false/> <key>ResetHwSig</key> <false/> <key>ResetLogoStatus</key> <false/> </dict> </dict> <key>Booter</key> <dict> <key>Quirks</key> <dict> <key>AvoidRuntimeDefrag</key> <true/> <key>DevirtualiseMmio</key> <false/> <key>DisableSingleUser</key> <false/> <key>DisableVariableWrite</key> <false/> <key>DiscardHibernateMap</key> <false/> <key>EnableSafeModeSlide</key> <true/> <key>EnableWriteUnprotector</key> <true/> <key>ForceExitBootServices</key> <false/> <key>ProtectCsmRegion</key> <false/> <key>ProvideCustomSlide</key> <false/> <key>SetupVirtualMap</key> <true/> <key>ShrinkMemoryMap</key> <false/> </dict> </dict> <key>DeviceProperties</key> <dict> <key>Add</key> <dict> <key>PciRoot(0x1)/Pci(0x2,0x0)</key> <dict> <key>layout-id</key> <data> BwAAAA== </data> </dict> </dict> </dict> <key>Kernel</key> <dict> <key>Add</key> <array> <dict> <key>BundlePath</key> <string>Lilu.kext</string> <key>Enabled</key> <true/> <key>ExecutablePath</key> <string>Contents/MacOS/Lilu</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> <dict> <key>BundlePath</key> <string>AppleALC.kext</string> <key>Comment</key> <string>Audio</string> <key>Enabled</key> <true/> <key>ExecutablePath</key> <string>Contents/MacOS/AppleALC</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> <dict> <key>BundlePath</key> <string>WhateverGreen.kext</string> <key>Comment</key> <string>Video card</string> <key>Enabled</key> <true/> <key>ExecutablePath</key> <string>Contents/MacOS/WhateverGreen</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> <dict> <key>BundlePath</key> <string>AppleMCEReporterDisabler.kext</string> <key>Enabled</key> <true/> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> <dict> <key>BundlePath</key> <string>AGPMInjector.kext</string> <key>Comment</key> <string>AGPM</string> <key>Enabled</key> <true/> <key>MatchKernel</key> <string></string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> </array> <key>Block</key> <array> <dict> <key>Enabled</key> <false/> <key>Identifier</key> <string>com.apple.driver.AppleTyMCEDriver</string> <key>MatchKernel</key> <string></string> </dict> </array> <key>Quirks</key> <dict> <key>AppleCpuPmCfgLock</key> <false/> <key>AppleXcpmCfgLock</key> <false/> <key>AppleXcpmExtraMsrs</key> <false/> <key>CustomSMBIOSGuid</key> <false/> <key>DisableIoMapper</key> <false/> <key>ExternalDiskIcons</key> <false/> <key>LapicKernelPanic</key> <false/> <key>PanicNoKextDump</key> <true/> <key>PowerTimeoutKernelPanic</key> <false/> <key>ThirdPartyTrim</key> <false/> <key>XhciPortLimit</key> <false/> </dict> </dict> <key>Misc</key> <dict> <key>Boot</key> <dict> <key>ConsoleBehaviourOs</key> <string>Graphics</string> <key>ConsoleBehaviourUi</key> <string>Text</string> <key>ConsoleMode</key> <string>Max</string> <key>HibernateMode</key> <string>None</string> <key>HideSelf</key> <true/> <key>PollAppleHotKeys</key> <false/> <key>Resolution</key> <string>1920x1080</string> <key>ShowPicker</key> <true/> <key>Timeout</key> <integer>20</integer> <key>UsePicker</key> <true/> </dict> <key>Debug</key> <dict> <key>DisableWatchDog</key> <false/> <key>DisplayDelay</key> <integer>0</integer> <key>DisplayLevel</key> <integer>2147483650</integer> <key>Target</key> <integer>0</integer> </dict> <key>Security</key> <dict> <key>AllowNvramReset</key> <true/> <key>ExposeSensitiveData</key> <integer>2</integer> <key>HaltLevel</key> <integer>2147483648</integer> <key>RequireSignature</key> <false/> <key>RequireVault</key> <false/> <key>ScanPolicy</key> <integer>0</integer> </dict> <key>Tools</key> <array> <dict> <key>Comment</key> <string>Not signed for security reasons</string> <key>Enabled</key> <false/> <key>Name</key> <string>UEFI Shell</string> <key>Path</key> <string>Shell.efi</string> </dict> <dict> <key>Comment</key> <string>Memory testing utility</string> <key>Enabled</key> <false/> <key>Name</key> <string>memcheck</string> <key>Path</key> <string>memcheck/memcheck.efi</string> </dict> </array> </dict> <key>NVRAM</key> <dict> <key>Add</key> <dict> <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key> <dict> <key>UIScale</key> <data> AQ== </data> </dict> <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key> <dict> <key>boot-args</key> <string>-v keepsyms=1 busratio=31</string> <key>csr-active-config</key> <data> ZwAAAA== </data> <key>prev-lang:kbd</key> <string>it:0</string> </dict> </dict> <key>Block</key> <dict> <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key> <array> <string>UIScale</string> </array> <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key> <array> <string>boot-args</string> </array> </dict> <key>LegacyEnable</key> <false/> <key>LegacySchema</key> <dict> <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key> <array> <string>EFIBluetoothDelay</string> <string>EFILoginHiDPI</string> <string>LocationServicesEnabled</string> <string>SystemAudioVolume</string> <string>SystemAudioVolumeDB</string> <string>bluetoothActiveControllerInfo</string> <string>bluetoothInternalControllerInfo</string> <string>flagstate</string> <string>fmm-computer-name</string> <string>nvda_drv</string> <string>prev-lang:kbd</string> </array> <key>8BE4DF61-93CA-11D2-AA0D-00E098032B8C</key> <array> <string>Boot0080</string> <string>Boot0081</string> <string>Boot0082</string> <string>BootNext</string> <string>BootOrder</string> </array> </dict> </dict> <key>PlatformInfo</key> <dict> <key>Automatic</key> <true/> <key>DataHub</key> <dict> <key>BoardProduct</key> <string>Mac-7BA5B2D9E42DDD94</string> <key>SystemProductName</key> <string>iMacPro1,1</string> <key>SystemSerialNumber</key> <string>REDACTED</string> <key>SystemUUID</key> <string>REDACTED</string> </dict> <key>Generic</key> <dict> <key>MLB</key> <string>REDACTED</string> <key>ROM</key> <data> </data> <key>SpoofVendor</key> <true/> <key>SystemProductName</key> <string>iMacPro1,1</string> <key>SystemSerialNumber</key> <string>REDACTED</string> <key>SystemUUID</key> <string>REDACTED</string> </dict> <key>PlatformNVRAM</key> <dict> <key>FirmwareFeatures</key> <string>3FF58FFD 00000000</string> <key>FirmwareFeaturesMask</key> <string>3FFF9FFF 00000000</string> <key>MLB</key> <string>REDACTED</string> <key>ROM</key> <data> </data> </dict> <key>SMBIOS</key> <dict> <key>BIOSReleaseDate</key> <string>09/17/2019</string> <key>BIOSVendor</key> <string>Apple Inc.</string> <key>BIOSVersion</key> <string>1037.0.78.0.0</string> <key>BoardAssetTag</key> <string></string> <key>BoardLocationInChassis</key> <string>Part Component</string> <key>BoardManufacturer</key> <string>Apple Inc.</string> <key>BoardProduct</key> <string>Mac-7BA5B2D9E42DDD94</string> <key>BoardSerialNumber</key> <string>REDACTED</string> <key>BoardType</key> <integer>10</integer> <key>BoardVersion</key> <string>1.0</string> <key>ChassisAssetTag</key> <string>iMacPro-Aluminum</string> <key>ChassisManufacturer</key> <string>Apple Inc.</string> <key>ChassisSerialNumber</key> <string>REDACTED</string> <key>ChassisType</key> <integer>9</integer> <key>ChassisVersion</key> <string>Mac-7BA5B2D9E42DDD94</string> <key>FirmwareFeatures</key> <string>3FF58FFD 00000000</string> <key>FirmwareFeaturesMask</key> <string>3FFF9FFF 00000000</string> <key>MemoryFormFactor</key> <string></string> <key>PlatformFeature</key> <integer>0</integer> <key>ProcessorType</key> <integer>0</integer> <key>SystemFamily</key> <string>iMac Pro</string> <key>SystemManufacturer</key> <string>Apple Inc.</string> <key>SystemProductName</key> <string>iMacPro1,1</string> <key>SystemSKUNumber</key> <string>Mac-7BA5B2D9E42DDD94</string> <key>SystemSerialNumber</key> <string>REDACTED</string> <key>SystemUUID</key> <string>REDACTED</string> <key>SystemVersion</key> <string>1.0</string> </dict> <key>UpdateDataHub</key> <true/> <key>UpdateNVRAM</key> <true/> <key>UpdateSMBIOS</key> <true/> <key>UpdateSMBIOSMode</key> <string>Create</string> </dict> <key>UEFI</key> <dict> <key>ConnectDrivers</key> <true/> <key>Drivers</key> <array> <string>apfs.efi</string> <string>VBoxHfs.efi</string> <string>ApfsDriverLoader.efi</string> <string>AppleGenericInput.efi</string> <string>AptioInputFix.efi</string> <string>FwRuntimeServices.efi</string> <string>UsbKbDxe.efi</string> </array> <key>Input</key> <dict> <key>KeyForgetThreshold</key> <integer>5</integer> <key>KeyMergeThreshold</key> <integer>2</integer> <key>KeySupport</key> <false/> <key>KeySupportMode</key> <string></string> <key>KeySwap</key> <false/> <key>PointerSupport</key> <false/> <key>PointerSupportMode</key> <string></string> <key>TimerResolution</key> <integer>50000</integer> </dict> <key>Protocols</key> <dict> <key>AppleBootPolicy</key> <false/> <key>AppleEvent</key> <false/> <key>AppleImageConversion</key> <false/> <key>AppleKeyMap</key> <false/> <key>AppleUserInterfaceTheme</key> <false/> <key>ConsoleControl</key> <true/> <key>DataHub</key> <false/> <key>DeviceProperties</key> <false/> <key>FirmwareVolume</key> <false/> <key>HashServices</key> <false/> <key>UnicodeCollation</key> <false/> </dict> <key>Quirks</key> <dict> <key>AvoidHighAlloc</key> <true/> <key>ClearScreenOnModeSwitch</key> <false/> <key>ExitBootServicesDelay</key> <integer>0</integer> <key>IgnoreInvalidFlexRatio</key> <false/> <key>IgnoreTextInGraphics</key> <true/> <key>ProvideConsoleGop</key> <true/> <key>ReconnectOnResChange</key> <false/> <key>ReleaseUsbOwnership</key> <false/> <key>ReplaceTabWithSpace</key> <false/> <key>RequestBootVarRouting</key> <false/> <key>SanitiseClearScreen</key> <true/> <key>UnblockFsConnect</key> <false/> </dict> </dict> </dict> </plist>

I'm afraid I can't test this, I think a BLE is needed (which I don't have) or an airport card (which I don't have) And my second device would be an early 2008 macbook pro which isn't compatible too.

Just to share some info if anyone has external usb wifi, such as alfa network awus devices. I have a awus036nh usb wifi: at the time of writing, alfa network does not have any working driver for Catalina (10.15 and 10.15.1). I found that this package works well and it's stable: https://github.com/chris1111/WIFI-Dlink-Catalina-Panel-V2 It works for these chipsets: RT3572,RT3072,RT3070,RT3573,MT7610,MT7610,MT7610, RT5370,RT2870,RT3071,RT2770,RT3573,RT5572,RT3573, RT3573,RT5572,RT3572 Mine is RT2870.

Hi, I don't think so, vm is different from a real hackintosh, and most probably if you look at your ioreg you will not see any EHC1 nor EHC2. You should see usb ports into a bridge (for example, look at my image in my previous post for the Fresco logic controller, which is passed through). I found some difficulties in making usb ports working in mac os: passing through is very easy, making usb ports to work in mac os is another story. You could try the GenericUSBXHCI.kext : this was buggy for my setup (some kernel panic if usb device was attached to a usb port at boot, usb mass storage not mounted at first time when plugged in), so in the end I bought an Inateck pci card (chipset FL1100) for 19,90 Euro, 5 minutes to install it, no kexts, no headaches, no problems at all. With this setup I'm using 2 emulated controllers in Unraid with usb of my motherboard (UHCI for usb 1.1 and EHCI for usb 2.0) --> devices attached to these controllers are fixed (like webcam, mouse/keyboard dongle), and they do not need to be attached at every boot of the vm (this is achieved by saving the vm settings in xml view). The 4 ports of the Inateck are used for mass storage devices, usb token for digital signatures, usb external wifi.

Is the disable x86 cpu topology patch specific to AMD/Ryzen? Cannot make it to work with intel cpu..

Hi all, I'm trying to understand more about usb in mac os/unraid. I know that in mac os (starting from 10.11?) there is a 15 ports limit: however, I cannot find anywhere if this 15-ports-limit refers to the total number of usb ports or to the total number of ports for each controller? This is my setup: 1- EHCI controller in Unraid, used to passthrough single USB devices (USB 2.0) --> HD pro webcam c920 always attached, in the attached picture there's also a mass storage device attached 2- UHCI controller in Unraid, used to passthrough the usb dongle of my microsoft desktop wireless 800 for keyboard/mouse (USB 1.1): always attached (P.S.: I was thinking it was usb 2.0, apparently not...) 3- Fresco logic FL1100 controller (USB 3.0 and USB 2.0): in this case the whole controller is passed through Total number of ports is 16, so if the 15-ports-limit is referred to total I'm not ok, if it's referred to total for each controller I'm ok..I think (and I hope) that the port limit is referred to each controller.. From all the videos I saw the problem was that not all the ports were listed under the XHC tree (on real hackintosh, not emulated), because of this limit, but since we have different bridges for different controllers it should not be a problem for us (qemu ehci controller has 6 ports, qemu uhci controller has 2 ports, so each controller is always below the limit). By the way, in unraid the code: <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> adds a qemu mouse and a qemu keyboard: I deleted it from my template, but for what purpose is it used?Maybe related to override of PS/2 mouse/keyboard?

Just for completeness: UsbInjectAll kext should be used only temporarly: what it does is to inject all the usb ports; if coupled with the port-limit patch you can then map your ports and understand what ports you are using, so to create an SSDT patch to limit to the ports you are using. It is wrong to apply the port limit patch and use UsbInjectAll, it can cause problems (it causes access outside a fixed array bounds).

I'm not able to see the source inside the attached kext, but from other references online I would say that inside this kext there are the references to the usb ports you are using --> this kext injects some of the usb ports (only the ports you are using) because of the port limit number. It should have the template of the usbinjectall kext, without injecting all the ports.

Reading some web pages around about AppleBusPowerController: it seems that from mac os Sierra some properties related to current and usb are injected in AppleBusPowerController. From my ioreg I couldn't see AppleBusPowerController loaded so I created SSDT-EC-USBX.aml and put it in CLOVER/acpi/patched folder. Source of SSDT-EC-USBX is: DefinitionBlock("", "SSDT", 2, "hack", "EC-USBX", 0) { Device(_SB.EC) { Name(_HID, "EC000000") } Device(_SB.USBX) { Name(_ADR, 0) Method (_DSM, 4) { If (!Arg2) { Return (Buffer() { 0x03 } ) } Return (Package() { // these values from iMac17,1 "kUSBSleepPortCurrentLimit", 2100, "kUSBSleepPowerSupply", 5100, "kUSBWakePortCurrentLimit", 2100, "kUSBWakePowerSupply", 5100, }) } } } This code is from RehabMan who says that EC and USBX must be injected in ioreg. However, here: https://olarila.com/forum/viewtopic.php?t=11144 Ewerd is saying that: "AppleBusPowerController.kext has changed in Catalina, it no longer matches to EC. The upshot of this has been that I don't need EC or USBX to get USB power. I've added a section for AppleBusPowerController to the top of my SSDT-UIAC:" DefinitionBlock ("", "SSDT", 2, "hack", "_UIAC", 0) { Device(UIAC) { Name(_HID, "UIA00000") Name(RMCF, Package() { "AppleBusPowerController", Package() { "kUSBSleepPortCurrentLimit", 0x0834, "kUSBSleepPowerSupply", 0x125C, "kUSBWakePortCurrentLimit", 0x0834, "kUSBWakePowerSupply", 0x125C }, But from ioreg it seems that EC and USBX are loaded and AppleBusPowerController is loaded too, so I should be ok..Am I right? EC: USBX: AppleBusPowerController: SSDT-EC-USBX.aml SSDT-EC-USBX.dsl

Thanks @Leoyzen I will read and investigate: do you refer to fl1100 chipset/Inateck card or other chipsets/cards? Apparently I have no problems even without the kext, my mobile charges if attached to usb, pendrive and external devices work; all seems pretty stable with no interruption and no errors in log related to usb. I tried the new whatevergreen kext (v.1.3.5), not officially released yet: I'm not able to boot, here is the log. From what I'm reading the new modification to "fix handling agdpmod" is causing problems. EDIT: Fixed in WEG 1.3.5 + Lilu 1.4.0 panic(cpu 14 caller 0xffffff7f9d5da322): WhateverGreen: weg @ adgpmod=cfgmap has no effect on 10.13.4, use agdpmod=ignore Backtrace (CPU 14), Frame : Return Address 0xffffff83b13d3720 : 0xffffff801a339a3b 0xffffff83b13d3770 : 0xffffff801a470fe5 0xffffff83b13d37b0 : 0xffffff801a462a5e 0xffffff83b13d3800 : 0xffffff801a2e0a40 0xffffff83b13d3820 : 0xffffff801a339127 0xffffff83b13d3920 : 0xffffff801a33950b 0xffffff83b13d3970 : 0xffffff801aad17f9 0xffffff83b13d39e0 : 0xffffff7f9d5da322 0xffffff83b13d3ac0 : 0xffffff7f9d5d965a 0xffffff83b13d3b90 : 0xffffff7f9d5db0f4 0xffffff83b13d3be0 : 0xffffff7f9d5db0a5 0xffffff83b13d3c20 : 0xffffff7f9d55ad36 0xffffff83b13d3c80 : 0xffffff7f9d55b224 0xffffff83b13d3cb0 : 0xffffff7f9d55b1b5 0xffffff83b13d3cd0 : 0xffffff7f9d54d7db 0xffffff83b13d3d30 : 0xffffff801a9b3b3c 0xffffff83b13d3da0 : 0xffffff801a9c1ac9 0xffffff83b13d3df0 : 0xffffff801aa37fce 0xffffff83b13d3e40 : 0xffffff801aa19735 0xffffff83b13d3ef0 : 0xffffff801aa1922e 0xffffff83b13d3f50 : 0xffffff801aa1b9cd 0xffffff83b13d3fa0 : 0xffffff801a2e013e Kernel Extensions in backtrace: as.vit9696.Lilu(1.3.9)[68B45477-7A34-3B5F-9D85-C3D9D92A7B8A]@0xffffff7f9d545000->0xffffff7f9d5befff as.vit9696.WhateverGreen(1.3.5)[77A9B060-B5D0-39AC-88F7-50984CB70366]@0xffffff7f9d5bf000->0xffffff7f9d640fff dependency: as.vit9696.Lilu(1.3.9)[68B45477-7A34-3B5F-9D85-C3D9D92A7B8A]@0xffffff7f9d545000 dependency: com.apple.iokit.IOPCIFamily(2.9)[AA7C7A4F-9F5D-3533-9E78-177C3B6A72BF]@0xffffff7f9ad2f000 BSD process name corresponding to current thread: kernel_task Mac OS version: 19B88 Kernel version: Darwin Kernel Version 19.0.0: Thu Oct 17 16:17:15 PDT 2019; root:xnu-6153.41.3~29/RELEASE_X86_64 Kernel UUID: 7103CD47-857F-341E-8741-52DB4299191F Kernel slide: 0x000000001a000000 Kernel text base: 0xffffff801a200000 __HIB text base: 0xffffff801a100000 System model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94) System shutdown begun: NO Panic diags file available: YES (0x0) System uptime in nanoseconds: 10865800969 last loaded kext at 10862738394: >!AGraphicsControl 4.5.9 (addr 0xffffff7f9bf4b000, size 12288) loaded kexts: com.objective-see.lulu 1.2.0 as.vit9696.!AALC 1.4.3 as.vit9696.WhateverGreen 1.3.5 as.vit9696.Lilu 1.3.9 >!AGraphicsDevicePolicy 4.5.9 @AGDCPluginDisplayMetrics 4.5.9 @GeForce 14.0.0 >!AUpstreamUserClient 3.6.8 >!AMCCSControl 1.13 >!AHV 1 |IOUserEthernet 1.0.1 >!AFIVRDriver 4.1.0 >ACPI_SMC_PlatformPlugin 1.0.0 @nvidia.NVDAStartup 14.0.0 >!A!IMCEReporter 115 |IO!BSerialManager 7.0.1f1 >pmtelemetry 1 @Dont_Steal_Mac_OS_X 7.0.0 >!A16X50ACPI 3.2 >!A!ISlowAdaptiveClocking 4.0.0 >AudioAUUC 1.70 @filesystems.apfs 1412.41.1 |SCSITaskUserClient 422.0.2 >!AFileSystemDriver 3.0.1 >!A!I8254XEthernet 3.1.5 >!AAHCIPort 341.0.2 >!AVirtIO 1.0 @filesystems.hfs.kext 522.0.9 @!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1 @BootCache 40 @!AFSCompression.!AFSCompressionTypeZlib 1.0.0 @private.KextAudit 1.0 >!AACPIButtons 6.1 >!ARTC 2.0 >!ASMBIOS 2.1 >!AAPIC 1.7 $!AImage4 1 @nke.applicationfirewall 303 $TMSafetyNet 8 @!ASystemPolicy 2.0.0 |EndpointSecurity 1 >!AGraphicsControl 4.5.9 |IOAccelerator!F2 438.2.7 >!ASMBus!C 1.0.18d1 |IOSMBus!F 1.1 @nvidia.driver.NVDAGK100Hal 14.0.0 |IOAVB!F 800.17 >!ASSE 1.0 @nvidia.driver.NVDAResman 14.0.0 >!ASMBusPCI 1.0.14d1 |IONDRVSupport 568 >IOPlatformPluginLegacy 1.0.0 >IOPlatformPlugin!F 6.0.0d8 >!AHDA!C 283.14 |IOHDA!F 283.14 |IO!B!F 7.0.1f1 |IO!BPacketLogger 7.0.1f1 @plugin.IOgPTPPlugin 810.1 |IOEthernetAVB!C 1.1.0 |IOSkywalk!F 1 >!A16X50Serial 3.2 @!AGPUWrangler 4.5.9 @!AGraphicsDeviceControl 4.5.9 |IOSlowAdaptiveClocking!F 1.0.0 |IOGraphics!F 568 |IOAHCIBlock!S 316.40.3 >!AXsanScheme 3 >usb.IOUSBHostHIDDevice 1.2 >!UAudio 320.49 |IOAudio!F 300.2 @vecLib.kext 1.2.0 >usb.cdc 5.0.0 >usb.networking 5.0.0 >usb.!UHostCompositeDevice 1.2 >usb.!UXHCIPCI 1.2 >usb.!UXHCI 1.2 >usb.!UUHCIPCI 1.2 >usb.!UUHCI 1.2 |IOAHCI!F 290.0.1 >usb.!UEHCIPCI 1.2 >usb.!UEHCI 1.2 |IOSerial!F 11 @filesystems.hfs.encodings.kext 1 |IOSurface 269.6 >usb.!UHostPacketFilter 1.0 |IOUSB!F 900.4.2 >!AEFINVRAM 2.1 >!AEFIRuntime 2.1 |IOHID!F 2.0.0 $quarantine 4 $sandbox 300.0 @kext.!AMatch 1.0.0d1 >DiskImages 493.0.0 >!AFDEKeyStore 28.30 >!AEffaceable!S 1.0 >!AKeyStore 2 >!UTDM 489.41.1 |IOSCSIBlockCommandsDevice 422.0.2 >!ACredentialManager 1.0 >KernelRelayHost 1 >!ASEPManager 1.0.1 >IOSlaveProcessor 1 |IOUSBMass!SDriver 157.40.7 |IOSCSIArchitectureModel!F 422.0.2 |IO!S!F 2.1 |IOUSBHost!F 1.2 >!UHostMergeProperties 1.2 >usb.!UCommon 1.0 >!ABusPower!C 1.0 |CoreAnalytics!F 1 >!AMobileFileIntegrity 1.0.5 @kext.CoreTrust 1 |IOTimeSync!F 810.1 |IONetworking!F 3.4 |IOReport!F 47 >!AACPIPlatform 6.1 >!ASMC 3.1.9 >watchdog 1 |IOPCI!F 2.9 |IOACPI!F 1.4 @kec.pthread 1 @kec.Libm 1 @kec.corecrypto 1.0 So, take care and always backup before updating.

I just installed in my box the Inateck kt4006 card: it has 2 usb 3.0 ports (external) and one 19 pins connector for additional 2 ports (to connect for example 2 ports on the front panel of the case). As supposed, it works out of the box in mac os, I tried with catalina 10.15.1 (19B88): it automatically loads the AppleUSBXHCIFL1100 driver, so no need to install any third party kext. I have no problems and it has the RESET option. Just modify the Syslinux Configuration (to append vfio-pci.ids) of Unraid OS and passthrough the pci device to the vm.

did you try adding the passwd attribute to vnc? Something like this: <graphics type='vnc' passwd='foo'> Se here also:

Type is wrong, instead of raw set it to qcow2.