| 33 | | The test builds are not going through Apple's notarization (would be too much effort to do this for every test build we upload). This means if you're using macOS 10.14.5 or later the kernel extensions will not load if you're using the default security settings. If you really want to use such a test build, you need to disable [https://developer.apple.com/library/archive/documentation/Security/Conceptual/System_Integrity_Protection_Guide/ConfiguringSystemIntegrityProtection/ConfiguringSystemIntegrityProtection.html System Integrity Protection] (as long as you're running test builds, we're strongly encouraging you to re-enable SIP once you're back to using an official release of !VirtualBox). None of these test builds currently work on Macs with M1 CPU. |
| | 33 | The test builds are not going through Apple's notarization (would be too much effort to do this for every test build we upload). This means if you're using macOS 10.14.5 or later the kernel extensions will not load if you're using the default security settings. If you really want to use such a test build, you need to disable [https://developer.apple.com/library/archive/documentation/Security/Conceptual/System_Integrity_Protection_Guide/ConfiguringSystemIntegrityProtection/ConfiguringSystemIntegrityProtection.html System Integrity Protection] (as long as you're running test builds, we're strongly encouraging you to re-enable SIP once you're back to using an official release of !VirtualBox). |
| | 34 | |
| | 35 | The test builds for macOS/ARM64 work in principle on Macs with M1 or M2 CPU. However, they are developer previews with known issues (including serious performance ones) with all recent guest operating systems. |
