Unexpected termination with exit code 1, after 10.13 upgrade

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
remerolle
Posts: 6
Joined: 18. Oct 2017, 12:55

Unexpected termination with exit code 1, after 10.13 upgrade

Post by remerolle »

I am seeing what I think is a similar issue since upgrading to High Sierra:

Code: Select all

The virtual machine 'test1' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
I was tryig to paste the code, but the forum saw the apple<dot>com in the output and said
You must be a member for 1 days and have 1 posts before you can post urls.
So, please see my text attachments.

Thanks for the help!
Attachments
vBox-installed.txt
(6.05 KiB) Downloaded 14 times
clean-system.txt
(5.39 KiB) Downloaded 6 times
socratis
Site Moderator
Posts: 27330
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: Unexpected termination with exit code 1, after 10.13 upgrade

Post by socratis »

I split your post from the thread "VirtualBox fails to run on macOS High Sierra - kernel driver not loaded", since you clearly do *NOT* have the same issue. An error message can be due to a lot of things, even if it has the same error code. You didn't even have the same error code, why would you think that it's the same problem? Yours is definitely not due to the kernel extension not being loaded, they load just fine:
  • MBPro:~ user-user$ kextstat | grep -v com.apple
    Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
       59    3 0xffffff7f80a3e000 0xf000     0xf000     com.symantec.kext.internetSecurity (5.2.2f12) BD0ACF56-FC15-3325-92A6-2493D52C2D89 <5 4 3 1>
       60    1 0xffffff7f80a4d000 0x70000    0x70000    com.symantec.kext.ndcengine (1.0f2) no UUID <59 4 1>
       61    0 0xffffff7f80d86000 0xb000     0xb000     com.symantec.kext.ips (3.5.1f12) no UUID <60 59 5 4 3 1>
       96    1 0                  0x1a0      0x1a0      com.websense.endpoint.process.kpi (8.3.0) 9024D506-A999-4C71-9995-34635A8525B5
       97    1 0xffffff7f822fe000 0x2a000    0x2a000    com.websense.endpoint.process (8.3) BCADF8F3-C4EF-3D6E-98F7-6BEABA5D2618 <96 7 5 4 1>
       98    0 0xffffff7f82328000 0x2a000    0x2a000    com.websense.endpoint.dlp (8.3) 4DBA961E-DA34-3754-AEF3-DC53C484E0DA <97 5 4 3 1>
      169    0 0xffffff7f86521000 0x4000     0x4000     com.symantec.kext.SymAPComm (100.1f12) 4D8A9157-A274-3480-85E2-C1F20A81AD1E <59 7 5 4 1>
      170    0 0xffffff7f86525000 0x20000    0x20000    com.sourcefire.amp.fileop (1.2.3) 78DBD9BF-83AB-3E95-B393-F5850D770D41 <5 4 1>
      175    0 0xffffff7f86589000 0xb000     0xb000     com.sourcefire.amp.nke (1.2.3) 7574115E-2824-3FF8-A376-2B069CDC96E0 <5 4 1>
      207    3 0xffffff7f82956000 0x62000    0x62000    org.virtualbox.kext.VBoxDrv (5.1.30) 84DA15FE-3565-342D-99EA-5DB4BE28B54F <7 5 4 3 1>
      208    0 0xffffff7f829df000 0x8000     0x8000     org.virtualbox.kext.VBoxUSB (5.1.30) BDD590D1-3A93-34A8-BF61-4A2A83487149 <207 198 52 7 5 4 3 1>
      209    0 0xffffff7f83c94000 0x5000     0x5000     org.virtualbox.kext.VBoxNetFlt (5.1.30) BA7273E5-779A-3246-A2B5-220DAD7B95C6 <207 7 5 4 3 1>
      210    0 0xffffff7f83c99000 0x6000     0x6000     org.virtualbox.kext.VBoxNetAdp (5.1.30) CBDE5D9F-0224-3A7E-9443-E8939BB79CB4 <207 5 4 1>
I'll need to do a bit further of analysis in the afternoon to see what might be going on with your setup, but I can see that you have 3 (three) different pieces of software that are "protecting" your OSX. I would start uninstalling them one by one and see who's the culprit; Symantec, Websense and Cisco SourceFire.

PS. Kudos for studying previous threads and submitting the appropriate information!
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.
remerolle
Posts: 6
Joined: 18. Oct 2017, 12:55

Re: Unexpected termination with exit code 1, after 10.13 upgrade

Post by remerolle »

Yea my apologies for submitting to that thread, I assumed it was a similar issue since it started with high serria. I should have done some further investigation.

Thanks!
remerolle
Posts: 6
Joined: 18. Oct 2017, 12:55

Re: Unexpected termination with exit code 1, after 10.13 upgrade

Post by remerolle »

I'll take a look at the software for this laptop installed by my helpdesk, but it all was "protecting" before the update to 10.13. Much of this software is disabled from taking active prevention measures given the challenges this active enforcement and my own Infra and development work.
socratis
Site Moderator
Posts: 27330
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: Unexpected termination with exit code 1, after 10.13 upgrade

Post by socratis »

Did you re-install VirtualBox after the 10.13 upgrade? Did you install the Supplemental Update for 10.13? Can you try with the just released VirtualBox 5.2.0?
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.
remerolle
Posts: 6
Joined: 18. Oct 2017, 12:55

Re: Unexpected termination with exit code 1, after 10.13 upgrade

Post by remerolle »

I first noticed this issue after upgrading to 10.13 public release. I promptly reinstalled to the latest version after I noticed the issue.

I just installed the Supplemental Update yesterday and it did not help.

I installed to 5.2.0 after you advised me, and no improvement. The GUI's error message looks prettier though!
socratis
Site Moderator
Posts: 27330
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: Unexpected termination with exit code 1, after 10.13 upgrade

Post by socratis »

remerolle wrote:no improvement. The GUI's error message looks prettier though!
Hey, that's an improvement right there! ;)

I still think that something might be wrong with your installed software that is interfering with the proper secure operation of VirtualBox. As I mentioned, please uninstall all of them and start adding them back one at a time, while testing VirtualBox in-between.
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.
remerolle
Posts: 6
Joined: 18. Oct 2017, 12:55

Re: Unexpected termination with exit code 1, after 10.13 upgrade

Post by remerolle »

I will go through that tomorrow. And after that I will start fresh with a clean install. I’ll report back my findings.

Thanks for working with me!
socratis
Site Moderator
Posts: 27330
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: Unexpected termination with exit code 1, after 10.13 upgrade

Post by socratis »

Thank you for being willful to try it, even go as far as reinstalling OSX !
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.
Mr. Tee
Posts: 6
Joined: 25. Jul 2016, 13:18

Re: Unexpected termination with exit code 1, after 10.13 upgrade

Post by Mr. Tee »

Had the same error code after upgrading to virtual box 5.2. (after Mac OS 10.13 upgrade)

In my case the virtual box extension pack wasn't upgraded so i did the following:
1) Start virtual box and check for updates
2) First it says everything is up to date but a few moments later the update link for the extension pack pops up
3) Installed new extension pack
4) All vm´s could be started as before
remerolle
Posts: 6
Joined: 18. Oct 2017, 12:55

Re: Unexpected termination with exit code 1, after 10.13 upgrade

Post by remerolle »

My extension pack was st the same latest version as the virtual box install.

I reinstalled macOS to 10.13 and no issues since.

Thanks!
socratis
Site Moderator
Posts: 27330
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: Unexpected termination with exit code 1, after 10.13 upgrade

Post by socratis »

Great, thanks for the feedback. Do you feel confident enough to mark this topic as [Solved]? I've always said that VirtualBox doesn't fail in a clean installation, but that's not always the suggested method of "fixing" potential issues... ;)
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.
Post Reply