FWIW, VB 5.1.24 crashes immediately when you try to open VB preferences.
running High Sierra 10.13 Beta (17A306f)
Crash: VirtualBox 5.1.24
-
- Volunteer
- Posts: 8851
- Joined: 30. Apr 2009, 09:45
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: just about all that run
Crash: VirtualBox 5.1.24
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
There are three groups of people. Those that can count and those that can't.
-
- Volunteer
- Posts: 8851
- Joined: 30. Apr 2009, 09:45
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: just about all that run
Re: Crash: VirtualBox 5.1.24
Error message.
- Attachments
-
- Error.txt.zip
- (20.17 KiB) Downloaded 43 times
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
There are three groups of people. Those that can count and those that can't.
-
- Oracle Corporation
- Posts: 3362
- Joined: 7. Jun 2007, 09:11
- Primary OS: Debian Sid
- VBox Version: PUEL
- Guest OSses: Linux, Windows
- Location: Dresden, Germany
- Contact:
Re: Crash: VirtualBox 5.1.24
I assume this happens with older versions of VirtualBox as well?
-
- Volunteer
- Posts: 8851
- Joined: 30. Apr 2009, 09:45
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: just about all that run
Re: Crash: VirtualBox 5.1.24
Hi Frank. I don't know I didn't try any older versions. However, the issue seems to be resolved with 10.13 Beta (17A315i) which came out yesterday. I'll give it a few days before marking it solved.
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
There are three groups of people. Those that can count and those that can't.
-
- Oracle Corporation
- Posts: 3362
- Joined: 7. Jun 2007, 09:11
- Primary OS: Debian Sid
- VBox Version: PUEL
- Guest OSses: Linux, Windows
- Location: Dresden, Germany
- Contact:
Re: Crash: VirtualBox 5.1.24
Thanks for the information!
-
- Volunteer
- Posts: 8851
- Joined: 30. Apr 2009, 09:45
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: just about all that run
Re: Crash: VirtualBox 5.1.24
Just installed 5.1.26. It crashed when I tried to open Preferences as before on High Sierra 10.13 Beta (17A315i).frank wrote:I assume this happens with older versions of VirtualBox as well?
As it turns out restarting the Mac after installing VirtualBox solves the issue. Don't know why a restart is needed.
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
There are three groups of people. Those that can count and those that can't.
-
- Volunteer
- Posts: 708
- Joined: 3. Mar 2015, 07:27
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: Linux, macOS, Windows
Re: Crash: VirtualBox 5.1.24
Possibly due to the VirtualBox kext not re-loading properly which would be a High Sierra bug. Were there any 'interesting' messages in the system log?As it turns out restarting the Mac after installing VirtualBox solves the issue. Don't know why a restart is needed.
I had to reboot after enabling Oracle to load the kext the first time I ran VBox on 10.13. Somehow the problem you describe seems to be related.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Crash: VirtualBox 5.1.24
loukingjr wrote:Don't know why a restart is needed.
Apple changed their policy regarding non-Apple kext(s), even from trusted developers, see Technical Note TN2459.granada29 wrote:I had to reboot after enabling Oracle to load the kext the first time I ran VBox on 10.13.
- Did you get a warning about the VirtualBox kexts from Oracle?
- Did you have to go to the System Preferences to specifically allow Oracle?
- Do you believe that this might be something that has to do with the change in policy?
- Maybe a reboot is required to load a new extension and rebuild the kext cache?
- An OSX glitch as a result of the modified policy?
I had a "smooth" experience with an older beta (the 17A306f that loukingjr referred to) and 5.1.22. And I'm putting smooth in quotes because it had it's own bag of problems. Plus it was the last thing that my late 2011 MBP did before moving upstate with the rest of the puppies...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Volunteer
- Posts: 708
- Joined: 3. Mar 2015, 07:27
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: Linux, macOS, Windows
Re: Crash: VirtualBox 5.1.24
Apple changed their policy regarding non-Apple kext(s), even from trusted developers, see Technical Note TN2459.
- Did you get a warning about the VirtualBox kexts from Oracle?
- Did you have to go to the System Preferences to specifically allow Oracle?
- Do you believe that this might be something that has to do with the change in policy?
- Maybe a reboot is required to load a new extension and rebuild the kext cache?
- An OSX glitch as a result of the modified policy?
- It was a system level warning - a small modal window popped up.
- Yes -Oracle was already listed (probably as a result of attempting to load their kext) but was not enabled.
- Yes - I think they are trying to come up with a mechanism that requires authorisation to load 3rd party kexts.
- Yes - that would seem to be the case for now. Hopefully there will be an improvement as 10.13 matures, either macOS just doing the job and letting things proceed, or coming up with a 'Reboot now' dialog.
- A glitch for now - hopefully Apple will improve things - there has been a lot of feedback in the Apple Developer forum about loading 3rd party kexts and they seem to be taking notice.