

Thanks to everyone working on this, but I just tried it with: We expect VirtualBox to be developped as a critical product - not a hobby.

We are as large community of users who rely on VirtualBox for our day to day work. Some have also reduced the number of kernel extensions and even provide an option to control that. They have updated their code so as to work correctly with Catalina. It has been widely publicized and is well known among Apple developers.

It exists since Catalina came out two years ago. Not six months later while you figure out how to make it work.Īlso the change in the way kernel extensions work is not new. The ultimate goal is that VirtualBox works out-of-the box with Big Sur the day it comes out. It makes sense that VirtualBox is not *supported* on Big Sur yet - meaning nobody should use VirtualBox on Big Sur for any production work.īut does not prevent the VirtualBox developers from updating the product so it works on beta releases of Big Sur, and make that available - also as a beta release - so that all of us, early testers of Big Sur, can give feedback on VirtualBox too. The very reason why Apple offers beta releases of macOS is precisely so that developers can make sure their products work on the platform at day 0, when it is released. MacOS BigSur is not supported by VirtualBox currently and until there is a final release it won't be.
