Driftwood

https://audiosex.pro/threads/sip-enabled-for-steinberg-and-v-r-stuff.74681/ Wondering if these SIP workaround techniques could be used for VBox ?

@tomnic As I'm currently using Sonoma 14.2 (23C64) apparently there was a cursor / pointing device bug with this version of the OS from what I was reading somewhere and I think its not been helping the vbox guests with sluggish 'forgetful' performance. Whats the latest version of Sonoma (14.4.1) been like with pointer control in VBox guests?

For Win 10 32-bit SYSTEM setup I'm finding this seems to work best / quickest.

@tomnic Ive updated the above to see if you spot any additions I need!

Hi Tomnic, Nice guide. Ive tried this with 6.1.50 and everything working installing Win 10 guest into the Box Host on Sonoma(in the process installing Win 32bit apps I needed etc...) but on reboot and resetting NVRAM SIP to 0000000 & removing the AMFIPass kext in config.plist its back to the kernel error cant load. Any info on this? BTW I used AMFIPass v1.40 and didn't require the bootflag -amfipassbeta METHODOLOGY 1. In config.plist (see image) inside your boot EFI, Add the numbers csr-active-config = 03080000 (see image) into the NVRAM section of config.plist (to workaround security & Privacy Oracle Box kext sign problems with this partial SIP disable). 2. Add AMFIPass.kext details (see image) into kernel section of config.plist. Save config.plist back to the EFI /OC folder. 3. Download version 1.40 of AMFIPass.kext and copy it over onto your EFI drive's Kext folder. 4. Ensure you can reset NVRAM in Opencore when rebooting 5. Reboot, and hit space, number to reset your NVRAM. 6. Now it should boot with your SIP disabled and use AMFIpass to allow the box kernel thru. 7. Download & install Vbox v.6.1.48 or 6.1.50 8. During the installation process it should ask you to sign / allow the Oracle Virtual Box / ALLOW it inside your 'System Settings' Security & privacy section. 9. After install and the kernel of box has been signed it will ask to reboot. Go ahead and reboot. 10. After reboot, locate and download/install Oracle_VM_VirtualBox_Extension_Pack-6.1.50.vbox-extpack (if using ver 6.1.50) 11. Now grab a ISO from Microsoft and install your guest OS - in my case it was Windows 10 32 bit iso 12. Go thru the motions of installing the guest OS like you normally would. 13. Locate and download VBoxGuestAdditions_6.1.50.iso or VBoxGuestAdditions_6.1.48.iso and install them from a guest ISO storage drive.This will provide a number of addition hardware features and functionality. 14. Finally, fine tune your guest OS for display USB pointing devices etc... 15. If you get problems running virtual box - quit Vbox completely (stop any guest VMs running first if you can) and then rerun it by running it from within Applications folder and not as an alias as sometimes aliases get corrupted or lose sight of the software. 16 I tried then resetting SIP to Enabled and disabling AMFIPass kext inside config plist Kernel section, reboot, resetting NVRAM and booting up to Sonoma but the Kernel errors reappeared and I found they were no longer 'Allowed' by the OS. Subsequently, virtual box guest VM's failed to start. 😞 17. So went back to partially Disabling SIP (csr-active-config = 03080000) but didn't require AMFIPass to ON now that Ive installed vBox. More on this soon... useful links: Virtual Box Old Builds: https://www.virtualbox.org/wiki/Download_Old_Builds_6_1 and https://download.virtualbox.org/virtualbox/6.1.50/ to find the Guest Additions etc... AMFIPass kext: https://community.macmeup.com/index.php?/files/category/3-kexts/. or payloads/Kexts/Acidanthera/AMFIPass-v1.4.0-RELEASE.zip

Any news on the 7970X 32 core 64 thread working under Sonoma?

14.2 beta ok too

Sonoma 14.1 23B74 all good on TRX40.

And you're not tempted by the Intel Core i9-14900K? 😉

So @fabiosun are you thinking the forthcoming 7975WX TRX50 will be viable?

@Jaidy PCIe 5.... Looking at the random write/read speeds its probably not worth it atm. Cache problems aside the tech looks great in theory. But we wait and see. As to the T700 not being stable under MacOS seems strange. Did you try Disk Utility in macOS Recovery to format the volume?

Sonoma 14.1 beta 3 TRX40 all good.

You should check resources - PCIE which ones are directly connected to CPU and which are to chipset. All devices inc USB devices are taking up resources. DO a count and subtract from the total available for your motherboard. Maybe take out a device - a drive, a GPU etc... (experiment) until you see a happy compromise. For example, The ASROCK TRX40 Creator features 88 PCIE lanes, 72 of which are useable to the end user. The Threadripper AMD CPUs utilise 56/64 PCIe 4.0 lanes. Chipset vs. processor allocated PCIe lanes The PCIe lanes on a motherboard originate either from the processor itself or the motherboard chipset. Generally, the processor lanes are reserved exclusively for the graphics card x16 slots and M.2 slots for high-speed SSDs, as they require to move data without being bottlenecked by the chipset. On the other hand, chipset lanes connect to onboard USB, other M.2 and PCIe slots, and SATA. The chipset itself transfers data to the processor via a dedicated 4-lane PCIe bus. So, all devices connected via PCIe lanes to the chipset will have a cap on their maximum bandwidth leading to bottlenecks Don't forget to run MMIO Opencore checks as u go.

Sonoma Beta 2 14.1 on TRX40 Asrock Creator 3970X all good.

Great to see the Fireface800 and TI Firewire PCIe card chipset still working in Sonoma! 🙂 DRIFTWOOD SONOMA 14.0 CONFIG PLIST (OC 0.9.5) for Asrock TRX40 Creator ATTACHED - not bothering with BT / Wifi in this config. Just Aquantia networking here! DRIFTWOOD-config.plist.zip