Make sure the kernel module has been loaded successfully mac os

Как исправить ошибку Kernel driver not installed (rc=-1908) в VirtualBox на macOS

Пользователи macOS (в особенности Big Sur) сталкиваются со следующей ошибкой при использовании виртуализации VirtualBox от Oracle:

Kernel driver not installed (rc=-1908)

Make sure the kernel module has been loaded successfully.

where: suplibOsInit what: 3
VERR_VM_DRIVER_NOT_INSTALLED
(-1908) — The support driver is not installed.
On linux, open returned ENOENT.

Исправить эту ошибку крайне просто. Вероятнее всего, причина её возникновения в том, что на этапе установки VirtualBox вы проигнорировали уведомление о том, что в настойках нужно предоставить одно из разрешений:

Чтобы исправить это, перейдите в «Системные настройки» macOS, откройте раздел «Защита и безопасность». В нём снимите замок в левом нижнем углу, а затем кликните на кнопку «Разрешить» рядом с появившемся пунктом «Загрузка системного ПО разработчика „Oracle America, Inc.” была заблокирована».

Если этого пункта у вас нет, попробуйте переустановить VirtualBox.

Источник

Kernel driver not installed (rc=-1908) Getting Errors in macOS Big Sur 11.0.1

I just want to work with VirtualBox but now I am getting this type of error.

I could not find a proper solution.

4 Answers 4

MAC with BIG SUR — Kernel driver not installed (rc=-1908)

Make sure the kernel module has been loaded successfully.

where the error is:

Download and install the latest VirtualBox 6.1.18 or higher. And then follow the below steps to resolve.

Step 2: Go into System Preferences->Security & Privacy

Step 3: Unlock the security center

Step 4: Approve the software by Oracle

Big Sur disables the VirtualBox kernel extensions as part of the installation process. You can verify this by running:

If the kernel extensions are installed, you will see something like this:

If you don’t see the extensions loaded, the easier fix is to delete your current VirtualBox app, download and install the lastest version and then go the Security & Privacy System Preferences Pane. You should see a message that some applications require a restart to work correctly.

Restart your Mac and VirtualBox should now work. You can re-run the kexstat command just to be sure the extensions were loaded.

Источник

virtualbox.org

End user forums for VirtualBox

• Board index‹General‹VirtualBox on Windows Hosts
• Change font size
• Print view

• FAQ
• Login

make sure the kernel module has been loaded successfully

make sure the kernel module has been loaded successfully

by StigmataLives » 2. May 2018, 16:26

Hi there,
I am very new to VirtualBox and never thought things would be so hard for me. I have been trying to install Linux flavor CentOS onVirtualBox from last 5 days but all I have ended up with is an error that has haunted many before me. I even tried the solutions but none of them worked for me and at last decided to post here, considering the fact that I might be missing something really valuable.

1st time, I installed VirtualBox ,VirtualBox-5.0.16-105871-Win, and later on I came to know via one of the thread that it’s no longer supported, so decided to go with other version. But before going for another version, I tried to work around with ExtPack, Oracle_VM_VirtualBox_Extension_Pack-5.0.16-105871a, but even that didn’t took me any where.
2nd time, I tried the latest version of VirtualBox , VirtualBox-5.2.8-121009-Win but even this didn’t help me out. I kept on getting the following error

NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034
STATUS_OBJECT_NAME_NOT_FOUND (0 retries) (rc=-101)
make sure the kernel module has been loaded successfully

Failed to open a session for the virtual machine mySys.

The virtual machine ‘mySys’ has terminated unexpectedly during startup with exit code 1 (0x1).
More details may be available in ‘\VirtualBox VMs\mySys\Logs\VBoxHardening.log’.
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine

Later on I read a thread where a guy was suggested to work with VirtualBox-5.1.26-117224-Win version, so i even downloaded same and tried it but no luck yet. I am still getting the same error

With above mentioned version of VirtualBox , I have even tried with different version of CentOS disk image file like CentOS-6.7-i386-minimal and CentOS-7-x86_64-Minimal-1708

I have already tried fixes suggested in a thread where user were asked to go C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv and manually install VBoxDrv.inf

Re: make sure the kernel module has been loaded successfully

by socratis » 2. May 2018, 16:49

1. Edit your post and get your names straight. There’s no VMWare VirtualBox. Fix this. If you can’t get the name of the product right I’m not sure how reliable the rest of the report is.

While you’re at the editing phase, ZIP your log and replace the text log with the ZIPPED version. Helps save a (virtual) tree or two.

Read the log. At the bottom. And follow the instructions in the last line:

Or try to re-install VirtualBox. Follow the steps below. If there is a failure, please state exactly which step failed :

Uninstall VirtualBox. Your VMs are going to be untouched. Reboot.

You may want to clean up your registry and/or filesystem at this point. CCleaner is a freeware utility that could help you. Mind the installation, it comes with «offers» from 3rd parties, known as «bundleware». Also, check out Device Cleanup program that helps you to remove any unused devices from your computer.

Download (if you haven’t already) the latest VirtualBox and its matching ExtPack. Store them in a common location, i.e. not on «Desktop», or «Documents», but to «Public/Downloads» for example.

Locate the downloaded file in Windows Explorer. Right-click on the installer and select » Run-as-Administrator «, even if you are the administrator . At the end of the installation, choose to «Start Oracle VM VirtualBox». Do not worry if your VMs do not show up.

If you’re going to install the ExtPack, go to File » Preferences » Extensions. Click on the icon with the orange, down-pointing arrow on the right. Select the ExtPack from the previous steps.

1. Quit VirtualBox. Re-start VirtualBox as you would normally, i.e. from the Desktop shortcut or the Start menu.

Re: make sure the kernel module has been loaded successfully

by StigmataLives » 2. May 2018, 19:09

Re: make sure the kernel module has been loaded successfully

by socratis » 2. May 2018, 21:47

I want you to try them once again. Slowly. Methodically. Read each instruction three times before you execute it.

If it still fails, re-install Windows (after a backup), something is wrong with your host, beyond the basic repair we can offer you over here.

Источник

Ticket #19795 (reopened defect)

Last modified 11 days ago

Virtualbox VM (Windows or Linux) crashes on Mac OS Bigsur host

Reported by:	hoshikawa2	Owned by:
Component:	other	Version:	VirtualBox 6.1.10
Keywords:	Cc:
Guest type:	all	Host type:	Mac OS X

Description

When I try to open a VM (does not matter if Windows or Linux), the error occur

Kernel driver not installed (rc=-1908)

Make sure the kernel module has been loaded successfully.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) — The support driver is not installed. On linux, open returned ENOENT.

Attachments

Change History

Changed 14 months ago by hoshikawa2

• attachmentCleanShot 2020-08-05 at 12.11.07.png added

comment:1 Changed 14 months ago by ausmartway

Having exactly the same issue.

comment:2 Changed 14 months ago by ausmartway

I am running 6.1.12, same issue

comment:3 Changed 14 months ago by ausmartway

updated to 6.1.13, same issue

comment:4 Changed 14 months ago by atiensivu

Happens with the test build 6.1.13 r139583 Using Mac OS 11 (20A5343i)

There will be many other broken apps too, because the kext’s have new restrictions and other changes that seem to be breaking things.

This is above my coding ability but it does look like there is a way to support the native hypervisor added to recent OSX versions: https://developer.apple.com/documentation/hypervisor

comment:5 follow-up: ↓ 7 Changed 14 months ago by aeichner

• Status changed from new to closed
• Resolution set to invalid

There is no point in constantly trying out new test builds and reiterating what we already know. macOS BigSur is not supported by VirtualBox currently and until there is a final release it won’t be. We know about the new restrictions and will implement a solution when time permits and BigSur progressed further in development. Closing this defect for now.

comment:6 Changed 14 months ago by agodfrin

macOS BigSur is not supported by VirtualBox currently and until there is a final release it won’t be.

Sorry, but this is not a valid answer. 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. It makes sense that VirtualBox is not *supported* on Big Sur yet — meaning nobody should use VirtualBox on Big Sur for any production work.

But 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 ultimate goal is that VirtualBox works out-of-the box with Big Sur the day it comes out. Not six months later while you figure out how to make it work.

Also the change in the way kernel extensions work is not new. It exists since Catalina came out two years ago. It has been widely publicized and is well known among Apple developers. Other products use kernel extensions. They have updated their code so as to work correctly with Catalina. Some have also reduced the number of kernel extensions and even provide an option to control that.

We all expect the same from VirtualBox. We are as large community of users who rely on VirtualBox for our day to day work. We expect VirtualBox to be developped as a critical product — not a hobby.

comment:7 in reply to: ↑ 5 ; follow-up: ↓ 9 Changed 14 months ago by MyDimeIsUp

There is no point in constantly trying out new test builds and reiterating what we already know. macOS BigSur is not supported by VirtualBox currently and until there is a final release it won’t be. We know about the new restrictions and will implement a solution when time permits and BigSur progressed further in development. Closing this defect for now.

Exactly what agodfrin said. You all need to update VirtualBox for Mac OS, or else you’re going to lose to someone else who has initiative to build a virtual machine program for Mac with support for Mac OS 11. The point of the beta is to get applications to work for the upcoming releases.

This is just laziness from the Virtual Box team.

comment:8 Changed 14 months ago by YJSoft

This is not «Invalid».

VirtualBox not running on macOS 11 is «Valid» issue and GM Release will not fix this issue. Although this issue can be fixed only after stable version of macOS release, this issue should be opened until proper fix.

comment:9 in reply to: ↑ 7 Changed 14 months ago by aeichner

This is just laziness from the Virtual Box team.

And without knowing anything about the team size and what else is being worked this is just plain arrogant and rude.

As a matter of fact, the public BigSur Beta was released barely a month ago right during vacation/holiday time. Yeah the issue is valid, I never stated anything else, but BigSur is not officially released and therefore not supported right now, so this topic doesn’t belong to the public bug tracker. It is also not helpful to try out new testbuilds and reiterate that it still doesn’t work because we know that. When we implement support we will put up a new testbuild and actively ask users to try it out. I also never wrote that we will wait until the final release of BigSur and only then start adapting VirtualBox to work with it.

comment:10 Changed 13 months ago by aeichner

• Status changed from closed to reopened
• Resolutioninvalid deleted

comment:11 follow-up: ↓ 12 Changed 13 months ago by aeichner

The latest macOS Testbuild (revision >= r140568) has preliminary support for BigSur included. Any feedback is appreciated!

comment:12 in reply to: ↑ 11 Changed 13 months ago by erolsk8

Thanks to everyone working on this, but I just tried it with:

• VirtualBox-6.1.15-140568-OSX.dmg
• Command Line Tools for Xcode 12 beta 5 (version: 12.0.0.0.1.1597368733)

And I still get this:

comment:13 Changed 13 months ago by aeichner

Did you authorize loading of the kernel modules and reboot the system after installation? There should have been dialog prompting you about during installation. If that is the case I need the output of the following commands:

comment:14 Changed 13 months ago by aeichner

The latest Beta seems to have broken something again, probably related to upgrading. Can you try completely uninstalling VirtualBox and install it again in case you tried to do any upgrade? Then reboot and check whether it works, if it doesn’t try the following commands:

and report the output of these tools and

If the kernel modules appear to be loaded you can try to start a VM again.

comment:15 Changed 13 months ago by aeichner

Apparently loading the KEXTs during boot automatically has stopped working with the latest Beta 8, you have to execute the «sudo kextload. » commands once after every boot in order to run any VM (but they run afterwards), a fix is being investigated.

comment:16 Changed 13 months ago by erolsk8

I followed your instructions @aeichner, and it was solved after I ran those 4 kextload commands!

Thank you so much!

comment:17 Changed 13 months ago by hwchiu

Hi, I tried the latest version but still had the issue, here is my environment and related outputs.

1. Version 6.1.15 r140592 (Qt5.6.3)
2. MacOS Big Sur: 11.0 Beta (20A5374i)

It seems like those four kernel modules don’t be loaded. Thanks

comment:18 Changed 13 months ago by aeichner

Is there anything in dmesg related to VirtualBox?

comment:19 Changed 13 months ago by hwchiu

With reinstallation and re-authorize to load kernel modules, I can start the VM now. problem solved. Thanks for your help.

comment:20 Changed 13 months ago by h72837

I’m on beta 8. I first installed the latest stable build and then found out the mac os beta forum section and came accross this ticket

I installed the latest development build over the stable build and installation completed successfully

when the installation finished a popup came up saying some components related to virtualbox were blocked for security reasons so i allowed the components that were being blocked and restarted my pc

after that i tried to uninstall and reinstall virtualbox since I was getting the error

but i kept getting installation failed. I used the uninstall script from the development build package

here’s the link to two dmesg logs after running

the output of those four commands

here’s the output of

sudo kmutil dumpstate

here’s the output of

sudo kmutil showloaded

I’m also getting some crashes

comment:21 Changed 12 months ago by aeichner

Testbuilds got updated with a new 6.1 testbuild including a crash fix when clicking on anything in the GUI which opens a popup menu. For installation it is advised to completely uninstall the old VirtualBox install, reboot and then reinstall VirtualBox and reboot again to make sure that the old KEXTs are removed before the new ones are installed.

comment:22 Changed 12 months ago by h72837

I’m on the latest macos beta build 20A5384C I downloaded 140728, installed it with security options unlocked and when the security popup came up I rebooted to allow virtualbox components to run. Re-ran the installer and installation finished successfully. I’m able to run ubuntu x64 VM both headless and xfce. Windows 10 also runs. I didn’t have to run

and didn’t have to boot into Recovery Mode (Command+R) and access Terminal to disable SIP with command

here’s output logs jic

comment:23 Changed 12 months ago by wotchr

I’m seeing similar behaviour:-

On Big Sur Beta (20A5384c) with csrutil disabled and a fresh install via Recovery. Uninstalled previous VirtualBox, rebooted and installed VirtualBox 140728 with security options unlocked, but I get no security popup.

(Have disabled Gatekeeper so that “Allow apps downloaded from Anywhere” is ticked).

sudo kextload -b org.virtualbox.kext.VBoxDrv

sudo kextload -b org.virtualbox.kext.VBoxNetFlt

sudo kextload -b org.virtualbox.kext.VBoxNetAdp

sudo kextload -b org.virtualbox.kext.VBoxUSB

Am able to open VirtualBox, but existing and new Virtual Machines throw up the NS_ERROR_FAILURE

Result Code: NS_ERROR_FAILURE (0x80004005) Component: MachineWrap Interface: IMachine

Here’s the various outputs:-

comment:24 Changed 12 months ago by tyll

@wotchr: Do they boot in headless mode? I have the same issue but my VMs will start headless.

Edit: Never mind, I installed r140728 and the installation fails. VMs won’t start at all. It also fails trying to reinstall the previous version (r140592) where headless worked.

Edit 2: I got it installed again via

in a recovery Terminal (copied from https://forums.virtualbox.org/viewtopic.php?f=8&t=93133). They still only boot headless, though.

comment:25 Changed 12 months ago by wotchr

@tyll I mean to add that — yes they do boot in headless mode

comment:26 follow-ups: ↓ 28 ↓ 38 Changed 12 months ago by aeichner

Thanks for the feedback so far, there is a new testbuild available at the Testbuilds page which contains some fixes to the installer. When testing make sure that you have completely uninstalled VirtualBox and rebooted the host before attempting to install it again. Please also don’t disable SIP because we’re interested in feedback with everything enabled, the testbuild is fully signed and notarized so there should be no issue in that regard. The installer should show a prompt now to notify the user that a reboot is required but with a Beta 9 host here this doesn’t appear to work always and Apple doesn’t show any dialog either. So in any case you have to reboot again after installing VirtualBox (annoying but this is something we cannot change or work around in any way, this is enforced by Apple and their new style of loading KEXTs. ).

comment:27 Changed 12 months ago by wotchr

Success!! Great work — thanks!!

• Uninstalled and rebooted
• SIP Enabled
• Kept System Prefs closed
• Installation succeeded
• Installed Extensions pack
• Rebooted*
• Virtual Machine started up

• I’m on beta 9 and — as you suggested — didn’t get the prompt to reboot.

comment:28 in reply to: ↑ 26 Changed 12 months ago by reydelanada

Thanks for the feedback so far, there is a new testbuild available at the Testbuilds page which contains some fixes to the installer. When testing make sure that you have completely uninstalled VirtualBox and rebooted the host before attempting to install it again. Please also don’t disable SIP because we’re interested in feedback with everything enabled, the testbuild is fully signed and notarized so there should be no issue in that regard. The installer should show a prompt now to notify the user that a reboot is required but with a Beta 9 host here this doesn’t appear to work always and Apple doesn’t show any dialog either. So in any case you have to reboot again after installing VirtualBox (annoying but this is something we cannot change or work around in any way, this is enforced by Apple and their new style of loading KEXTs. ).

Sorry, did what you state and it’s not working here. I already had dsrutil disabled. Any command you find usefull please ask.

comment:29 Changed 12 months ago by aeichner

Please provide the output of the following commands executed in the specified order below:

comment:30 Changed 12 months ago by reydelanada

sudo kmutil load -b org.virtualbox.kext.VBoxDrv shows nothing.

comment:31 Changed 12 months ago by aeichner

The output clearly shows that the kernel modules are loaded, so something else must be gooing wrong for you. Can you attach the VBoxSVC.log and a VM log of the affected VM in case it is actually created?

comment:32 Changed 12 months ago by reydelanada

Please tell me the location of VBoxSVC.log

comment:33 Changed 12 months ago by reydelanada

comment:34 follow-up: ↓ 35 Changed 12 months ago by aeichner

Interesting, the VM you try to start has a saved state but VirtualBox can’t find it:

Can you check whether the file exist at that location?

comment:35 in reply to: ↑ 34 Changed 12 months ago by reydelanada

Interesting, the VM you try to start has a saved state but VirtualBox can’t find it:

Can you check whether the file exist at that location?

I already checked that, but there is no file there.

comment:36 Changed 12 months ago by reydelanada

I fixed the saved state issue. now it’s working 🙂

comment:37 Changed 12 months ago by aeichner

Uninstalling a KEXT is not working right now with the latest Beta as stated here (search for 64331929). When uninstalling VirtualBox you have to follow the mentioned workaround in order to fully uninstall the KEXTs.

comment:38 in reply to: ↑ 26 Changed 12 months ago by tyll

Replying to aeichner: Just wanted to chime in and confirm that as of r140753 the VMs open now. Thanks for fixing it!

comment:39 Changed 12 months ago by modym

I am on the most recent beta of Big Sur and on the most recent testbuild (as far as I know) r140809, however I am still receiving a «kernal driver not installed» error. when installing, I uninstalled the previous version, rebooted, installed r140809, and rebooted again. Am I missing something?

comment:40 follow-up: ↓ 43 Changed 12 months ago by Jasmin

I am currently on Big Sur build 20A5395g and have tried installing 140902 VirtualBox build. Results are that it installs, but I never see a Security Preferences pop up anything. I’ve tried uninstalling, rebooting, re-installing, keeping Security Preferences open and unlocked, tried with and without SIP. Tried also to set consent using spctl kext-consent add VB5E2TV963, but that didn’t work. When I run:

So stuck here at this point unless anyone can offer any further assistance on anything else I can try?

comment:41 Changed 11 months ago by rajatag

Issue continues with r141128 on Big Sur build 20A5395g

comment:42 in reply to: ↑ description Changed 11 months ago by haecker

Sorry for the comment, just trying to get on the CC list which seems impossible without making a comment.

comment:43 in reply to: ↑ 40 ; follow-up: ↓ 45 Changed 11 months ago by NickyD

I was able to get VirtualBox 6.1.16 r140961 running on BigSur macOS 11.0.1 (20B29) / Darwin 20.1.0

Step 2 — Go into System Preferences->Security & Privacy

Step 3 — Unlock the security center

Step 4 — Approve the software by Oracle

I am currently on Big Sur build 20A5395g and have tried installing 140902 VirtualBox build. Results are that it installs, but I never see a Security Preferences pop up anything. I’ve tried uninstalling, rebooting, re-installing, keeping Security Preferences open and unlocked, tried with and without SIP. Tried also to set consent using spctl kext-consent add VB5E2TV963, but that didn’t work. When I run:

So stuck here at this point unless anyone can offer any further assistance on anything else I can try?

comment:44 Changed 11 months ago by jalkmco9qi32

NickyD, Never get the «Approve the software by Oracle» trigger.

sudo kextload gets me a laundry list of unresolved dependencies.

Seems Oracle should have been working on this and not abandoned testing and just wait till the official release, as that causes users to have issues when they actually update.

comment:45 in reply to: ↑ 43 Changed 11 months ago by Jasmin

Still no progress, cannot proceed with Big Sur 11.0.1 and Virtual Box 6.1.97-141309. Never see any security pop ups, no matter what I try.

comment:46 Changed 11 months ago by qkdreyer

I’ve uninstalled Virtual Box, rebooted, installed latest 6.1.x test builds (https://www.virtualbox.org/download/testcase/VirtualBox-6.1.17-141348-OSX.dmg), and running the following command sudo kextload -b org.virtualbox.kext.VBoxDrv triggers the error :

comment:47 Changed 11 months ago by tom_vbox

It seems that the issue and a workaround are described here:

It seems to be an issue that virtualbox is not loading the extensions if SIP is modified. Hope this helps the developers to solve it. I would like to change my sip settings again for usage with other apps and scripts. Hopefully there will be a solution in the next release.

comment:48 Changed 11 months ago by jalkmco9qi32

Just to make sure, you have to boot to recovery mode to get this pile to work? Maybe oracle dev’s should have not kicked this can down the road with the arrogance of «we don’t support beta products» It’s not that you are supporting them, Beta exists for a reason, so YOU CAN MAKE SURE YOUR SOFTWARE WORKS when the actual release comes.

Hey at least I don’t pay for the product! If I did, I’d look for a competent vendor.

comment:49 follow-up: ↓ 52 Changed 11 months ago by TommiC

I’m now getting very frustrated with this. I have now used hours and hours for trying to reinstall Virtualbox 5.2 (the only version that works with our Vagrant box) and without any success. I have tried all of those «workarounds» and they are not working and I’m not seeing any security pop-ups.

comment:50 Changed 11 months ago by haecker

@all: I would suggest you guys all do the same that one has to do with a major system upgrade: Do your research first, check which mission critical applications you have, then _DO NOT UPDATE_ until you are sure that they all work. It’s not much googling and it’s the reason I’m on this bug — I want to know when it’s safe to upgrade because the Software I depend on works.

And while it doesn’t: I’m guessing you are liable to get all the money back you payed for this open source package. So maybe pack up your civility and either a) pay the developers some money to work on the issues you care about, or b) try to at least contribute something that helps them to do what you want.

I am sure they are already working on support — it’s inevitable. But software does take time.

comment:51 Changed 11 months ago by jalkmco9qi32

@haecker: Funny you say that but there is no way to «contribute» monetarily to the project, because it is OWNED BY ORACLE.

Oracle has $39.70 BILLION in Revenue for 2020 (wiki data, I can only assume its projected) Just over 1/4th of that is Operating Expense.

Some history:

— VirtualBox was first offered by Innotek GmbH from Weinstadt, Germany, under a proprietary software license, making one version of the product available at no cost for personal or evaluation use, subject to the VirtualBox Personal Use and Evaluation License (PUEL)

— Feb 2008, Sun Microsystems acquired Innotek

— May 2009, Oracle buys Virtual Iron Software — Server Virtualization Software

— Jan 2010 Oracle Corporation acquired Sun, re-branded the product as «Oracle VM VirtualBox»

— Feb 2016, Oracle buys Ravello Systems — Virtualization Company

Oracle bought up other virtualization software for network frame work and other facets. Fact is Oracle wanted into this market, we didn’t want Oracle. They bought it simply because they needed a virtualization software that THEY OWNED so they didn’t have to pay licensing costs to another company for their bread and butter products.

They support the product because they have to internally, but of course internally they don’t need the OSX product. They *NEED* the Linux and Solaris based product to continue to provide a bridge between current technology and legacy systems which many of their customer base is still on, in some form or fashion.

If they want to give this project back to the public domain to maintain and support then by all means do it.

But to make statements that «we don’t support dev products» when the specific reason any of these threads where started was to alert them that «a bug exists in a product that WILL BE RELEASED» which gives them ample time to troubleshoot and overcome the issue with a product. To think they would just kick this can down the road until the «actual prodcut» is released is total nonsense.

What if every vender did that? Then we would hear «we don’t support products until 90 days after release, 12 months after release, to allow ample time for the OS Provider to ‘work out their bugs’ then we act»

That logic is simply ludicrous. We gave them ample time and they just simply do not care. But that is the mainstay of all things Oracle, is why so many companies have simply moved away from their entire eco system. Just like MySQL, PostgreSQL, MongoDB, DB2, Google BigTable, Amazon.

Most of us that use Virtualbox are not just idiots running an old copy of XP or Win7, we are developers also.

But before you start banging out nonsense, which your above clearly is, there is NO WAY TO PAY DEVELOPERS FOR THE VIRTUAL BOX PROJECT.

comment:52 in reply to: ↑ 49 ; follow-up: ↓ 56 Changed 11 months ago by aeichner

I’m now getting very frustrated with this. I have now used hours and hours for trying to reinstall Virtualbox 5.2 (the only version that works with our Vagrant box) and without any success. I have tried all of those «workarounds» and they are not working and I’m not seeing any security pop-ups.

VirtualBox 5.2 is EOL and won’t get support for BigSur. The latest 6.1.16 release has support for it. It works on my local machine with SIP enabled etc. If this release doesn’t work for someone we need the exact error message and output from the commands mentioned in comment 13 and comment 14.

@jalkmco9qi32: Stop your off topic ramblings about things you have no clue about, next time I’ll remove them because they don’t add any information related to the issue. The OSX variant is used internally.

«If they want to give this project back to the public domain to maintain and support then by all means do it.»: VirtualBox is open source. We don’t prevent anyone from stepping up and submitting patches but for some reason we didn’t get anything so far from you.

«We gave them ample time and they just simply do not care» is a joke. _You_ didn’t gave us anything, especially when it comes to time time. It is just arrogant to assume that engineers have nothing else to do than waiting for Apple changing something fundamentally and immediately starting to implement support for it during the Beta cycle. Apple completely re-did their KEXT handling and there were issues throughout the different Betas with it blocking us from getting everything tested extensively, they even changed the kmutil command line tool completey in the last Beta.

Источник