Other

Good to know. I won't upgrade until that works, but I've never been an early adopter of mac os versions after 10.6 anyway. You can use the VM's Start button menu or you can use the Machine menu. As mentioned, you will have limited practical utility for this as an interactive machine unless you have already configured a way to remote control the VM via network. It was easier for me to just run Sonoma instead, despite the broken Wi-Fi.

It's broken in Ventura as far as we can tell. It works in Sonoma. If you absolutely must use Ventura, you can try starting the guests headless and then remote controlling them via SSH, VNC, RDP, etc, but you'd have to setup the the remote control services on the guest and the network bridging.

Thanks. SIP is disabled. The kext unload/load did not allow the VMs to start normally. I found another forum that mentioned that VBox 6.1.x on Ventura will not start VMs in normal mode, but that headless mode will start and then you can remote desktop into the VM. Headless start (only) does appear to work in Ventura after following your Sonoma guide -- the "preview" thumbnail in VBox shows the guest running normally. I have no clue why that is and VBox does not appear to be able to give useful logs for the failure when launching in normal mode. It does not appear to be a function of the guest VM settings, as I have tried to disable/toggle as much as possible on multiple guest OS types and headless start does not have any issues. Again, your guide works perfectly for Sonoma on AMD and VBox guests run normally, so apparently this broke in Ventura and was fixed in Sonoma.

Thank you very much for the guide @tomnic and @Driftwood. It works perfectly for VirtualBox 6.1.50 on my AMD hack Sonoma host, but I cannot get it to work on Ventura 13.6.9 on the same box using the same OC config (AMFIPass.kext confirmed loaded in Ventura). The odd thing is that the virtualbox kexts are loaded on Ventura without requiring any confirmation in Settings/Security (which is the finicky part on Sonoma): % kextstat -l | grep -i virtualbox Executing: /usr/bin/kmutil showloaded --list-only No variant specified, falling back to release 181 3 0xffffff7f9710e000 0xb8ff2 0xb8ff2 org.virtualbox.kext.VBoxDrv (6.1.50) 20DAAA76-AAB6-3E00-A62C-FCEB45D80CD1 <9 7 6 3 1> 182 0 0xffffff7f971f4000 0x4ffa 0x4ffa org.virtualbox.kext.VBoxUSB (6.1.50) 043FF80E-90D5-375A-842C-623AEF17A4B5 <181 180 74 9 7 6 3 1> 183 0 0xffffff7f971ef000 0x3ffc 0x3ffc org.virtualbox.kext.VBoxNetFlt (6.1.50) 3B8D8513-6061-3C02-8E8B-5ADA4EB2B341 <181 9 7 6 3 1> 184 0 0xffffff7f971e9000 0x1ff3 0x1ff3 org.virtualbox.kext.VBoxNetAdp (6.1.50) DD5AADC9-DC49-33F1-8FAF-C5166E143C51 <181 7 6 1> ...but yet VirtualBox gives the standard "Result Code: NS_ERROR_FAILURE (0x80004005)" error when I try to launch any guest. I'm in the process of upgrading this box from Catalina to Ventura or Sonoma, and the broken Wi-Fi in Sonoma is making me strongly consider Ventura for now. However, I need Box so it's a conundrum. I really imagined that if it worked for the more locked down Sonoma it would be straightforward for Ventura. Any thoughts? Thanks again; without this guide, I wouldn't even have the option for Sonoma.