start new VM report NS_ERROR_FAILURE (0x80004005)

Discussions related to using VirtualBox on Mac OS X hosts.

start new VM report NS_ERROR_FAILURE (0x80004005)

Postby froghui » 6. Oct 2019, 17:23

Hi, I've upgraded Mac OS from 10.13.6 to 10.14.6 today, and I found my old VirtualBox 5.0.26 did not work, so I downloaded the latest version 6.0.12, unfortunately, all my vms can not be started correctly, and it reported:
The virtual machine 'test7_default_1570372665423_51340' has terminated unexpectedly during startup with exit code 1 (0x1).

Details, Code: NS_ERROR_FAILURE (0x80004005)
Compnent: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

I suspected it was the notarization of new/updated kernel extensions being required on 10.14.5, but I tried it several times, this method did not work.

Then I tried 6.0.0, 6.0.8 and 5.2.30, none of the version fixed the issue.

I've uploaded the crash log (since I can not upload the whole crash file yet, I pasted the main part in the end), hope someone have encountered the same issue with me and can share some clue, thanks.
Code: Select all   Expand viewCollapse view
Process:               VirtualBoxVM [1285]
Path:                  /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM
Identifier:            VirtualBoxVM
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           VirtualBoxVM [1285]
User ID:               501

Date/Time:             2019-10-06 22:38:15.619 +0800
OS Version:            Mac OS X 10.14.6 (18G103)
Report Version:        12
Anonymous UUID:        1F619F8A-A67F-B18D-FE0D-5961B4E61DE0


Time Awake Since Boot: 180 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000110
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [1285]

VM Regions Near 0x110:
-->
    __TEXT                 0000000108796000-00000001087b8000 [  136K] r-x/rwx SM=COW  /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM

Application Specific Information:
crashed on child side of fork pre-exec

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libdispatch.dylib                0x00007fff75496e47 _dispatch_mgr_queue_push + 41
1   libdispatch.dylib                0x00007fff75492bab _dispatch_lane_resume_activate + 58
2   com.apple.CoreFoundation         0x00007fff49556e38 ____initDayChangedNotification_block_invoke + 187
3   libdispatch.dylib                0x00007fff7548d63d _dispatch_client_callout + 8
4   libdispatch.dylib                0x00007fff7548ed4b _dispatch_once_callout + 20
5   com.apple.CoreFoundation         0x00007fff49556d7b __initDayChangedNotification + 34
6   com.apple.CoreFoundation         0x00007fff4955469b __CFNotificationCenterGetLocalCenter_block_invoke + 155
7   libdispatch.dylib                0x00007fff7548d63d _dispatch_client_callout + 8
8   libdispatch.dylib                0x00007fff7548ed4b _dispatch_once_callout + 20
9   com.apple.CoreFoundation         0x00007fff495545fd CFNotificationCenterGetLocalCenter + 41
10  com.apple.CoreFoundation         0x00007fff495874cb _CFLocaleCopyCurrentGuts + 1310
11  org.qt-project.QtCoreVBox        0x00000001094849bd QSystemLocale::fallbackUiLocale() const + 621
12  org.qt-project.QtCoreVBox        0x00000001092707cd QLocalePrivate::updateSystemPrivate() + 157
13  org.qt-project.QtCoreVBox        0x00000001092715e3 0x1091e4000 + 579043
14  org.qt-project.QtCoreVBox        0x00000001092716be QLocale::QLocale() + 14
15  org.qt-project.QtCoreVBox        0x0000000109322aa2 0x1091e4000 + 1305250
16  org.qt-project.QtCoreVBox        0x000000010932142a 0x1091e4000 + 1299498
17  org.qt-project.QtCoreVBox        0x00000001093553f8 0x1091e4000 + 1512440
18  org.qt-project.QtCoreVBox        0x0000000109355172 0x1091e4000 + 1511794
19  org.qt-project.QtCoreVBox        0x00000001093028c3 QFileInfo::exists(QString const&) + 67
20  org.qt-project.QtCoreVBox        0x00000001091f84f3 0x1091e4000 + 83187
21  org.qt-project.QtCoreVBox        0x00000001091f8097 0x1091e4000 + 82071
22  org.qt-project.QtCoreVBox        0x00000001091f9ddf 0x1091e4000 + 89567
23  org.qt-project.QtCoreVBox        0x00000001091f8c89 QLibraryInfo::location(QLibraryInfo::LibraryLocation) + 41
24  org.qt-project.QtCoreVBox        0x0000000109359b32 0x1091e4000 + 1530674
25  org.qt-project.QtCoreVBox        0x00000001093ca1d6 QCoreApplicationPrivate::init() + 166
26  org.qt-project.QtGuiVBox         0x00000001097e2f71 QGuiApplicationPrivate::init() + 49
27  org.qt-project.QtWidgetsVBox     0x0000000109d9bd4e QApplicationPrivate::init() + 14
28  VirtualBox.dylib                 0x0000000108808ae9 TrustedError + 153
29  org.virtualbox.app.VirtualBoxVM   0x00000001087991f4 0x108796000 + 12788
30  org.virtualbox.app.VirtualBoxVM   0x000000010879932d 0x108796000 + 13101
31  org.virtualbox.app.VirtualBoxVM   0x000000010879c3e4 0x108796000 + 25572
32  org.virtualbox.app.VirtualBoxVM   0x00000001087998d2 0x108796000 + 14546
33  libdyld.dylib                    0x00007fff754da3d5 start + 1

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000100  rbx: 0x00007fc89d00e140  rcx: 0x00007fffabd55440  rdx: 0x0000000000000006
  rdi: 0x00007fffabd55440  rsi: 0x00007fc89d00e140  rbp: 0x00007ffee7462a10  rsp: 0x00007ffee74629e8
   r8: 0xff80004000000000   r9: 0x0000000000000006  r10: 0x00007fc89d00e140  r11: 0x0000002000000000
  r12: 0x00007fc89d00d0e0  r13: 0x00007fc89d1002b0  r14: 0x00007ffee74629ff  r15: 0x0000000000000000
  rip: 0x00007fff75496e47  rfl: 0x0000000000010206  cr2: 0x0000000000000110
 
Logical CPU:     4
Error Code:      0x00000006
Trap Number:     14
froghui
 
Posts: 4
Joined: 6. Oct 2019, 17:10

Re: start new VM report NS_ERROR_FAILURE (0x80004005)

Postby socratis » 7. Oct 2019, 07:51

You might want to print the following steps, or save them in a test file on your desktop, because there are a couple of reboots, and you don't want to go "hunting" in the forums...
  1. Download the latest release, or the latest test build (NOT the development snapshot), if you don't already have them.
  2. Reboot.
  3. Make sure you're part of the "admin" group. If you are logged in with the primary user account/owner, you are part of the admin group.
  4. Mount the DMG from the previous step. Run "VirtualBox_Uninstall.tool". Make sure there are no error messages. If there are, please post them, exactly as they appear.
  5. Reboot.
  6. Mount the DMG from the previous steps. Double-click the "VirtualBox.pkg". As soon as you start the installation, press Cmd+L to show the log. Select "Show All Logs" from the drop-down menu. Before the last step of the installation (Done), click the "Save" in the log window. ZIP and attach that file.
  7. Start VirtualBox. If it crashes, open "Console.app" and look at "~/Library/Logs". Is there a VirtualBox related log with the current date/time? ZIP and attach that file as well.
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.
socratis
Site Moderator
 
Posts: 27690
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: start new VM report NS_ERROR_FAILURE (0x80004005)

Postby froghui » 7. Oct 2019, 09:50

I've completed all the steps as you suggested, here are the result:
  1. download the 6.0.12 release;
  2. reboot
  3. make sure my account is part of admin group;
  4. uninstall the previous virtualbox successfully by "VirtualBox_Uninstall.tool";
  5. reboot;
  6. install the 6.0.12 successfully, the install log is attached;
  7. start the virtualbox, create a ubuntu VM from the wizard, then started the VM, the error is the same. The VM crash log is attached.
And this is the result of kextstat:
kextstat | grep -v com.apple
Index Refs Address Size Wired Name (Version) UUID <Linked Against>
57 2 0xffffff7f80e71000 0xf000 0xf000 com.symantec.internetSecurity.kext (14.0.1f215) 79A436BC-BBC2-37FB-9F83-92C2344FE725 <6 5 3 1>
58 0 0xffffff7f80e80000 0x18000 0x18000 com.symantec.nfm.kext (14.0.1f215) 7A81CC24-813F-3B6B-9633-D6B6A9AE36E1 <57 6 5 3 1>
59 0 0xffffff7f80ecb000 0x6b000 0x6b000 com.symantec.ips.kext (14.0.1f215) no UUID <57 6 5 3 1>
169 1 0 0x1a0 0x1a0 com.websense.endpoint.process.kpi (8.3.0) C41337A1-0EC3-3896-A954-A1F85E849D53
170 1 0xffffff7f83ad4000 0x2a000 0x2a000 com.websense.endpoint.process (8.3) 7FF8C957-4E54-3F49-88AC-D36C7A4C2A2F <169 8 6 5 1>
171 0 0xffffff7f83afe000 0x2a000 0x2a000 com.websense.endpoint.dlp (8.3) 30AAF0AC-B41D-3FDC-BCD4-270C5523A411 <170 6 5 3 1>
172 3 0xffffff7f83b28000 0xf0000 0xf0000 org.virtualbox.kext.VBoxDrv (6.0.12) 79AB3317-5F6D-3FE0-965C-92E45277AA0D <8 6 5 3 1>
174 0 0xffffff7f83c18000 0x8000 0x8000 org.virtualbox.kext.VBoxUSB (6.0.12) B1285DF7-2D17-3497-A948-40825951123A <173 172 54 8 6 5 3 1>
177 0 0xffffff7f83c20000 0x5000 0x5000 org.virtualbox.kext.VBoxNetFlt (6.0.12) C1B5DFEA-CB4C-30BD-9A92-C92391F7BDE0 <172 8 6 5 3 1>
178 0 0xffffff7f83c25000 0x6000 0x6000 org.virtualbox.kext.VBoxNetAdp (6.0.12) F8D3E46F-C4EA-397A-ACB1-EF2BF77C0506 <172 6 5 1>
181 0 0xffffff7f83c2b000 0x29c000 0x29c000 com.alibaba.kext.aliedr (1) FAAA6D34-F6DE-3084-8ABD-09BFCD2B6F44 <6 5 3 2 1>
182 0 0xffffff7f83ec7000 0x6000 0x6000 com.astrill.astrill.kext (1.0) 35C591CE-5DF2-A65B-3C4C-CE60D2301544 <8 6 5 1>

Any ideas? Thanks.
Attachments
VirtualBoxVM_2019-10-07-154136_shengymMacBook2-crash.txt
VM crash log
(50.83 KiB) Downloaded 14 times
installer-log-7-Oct-2019.txt
Virtualbox installer log
(18.96 KiB) Downloaded 12 times
froghui
 
Posts: 4
Joined: 6. Oct 2019, 17:10

Re: start new VM report NS_ERROR_FAILURE (0x80004005)

Postby froghui » 8. Oct 2019, 05:37

I just use the VBoxHeadless to start the VM, it starts. The log is attached as well, so the problem is in the normal start, can anyone share some ideas?

Code: Select all   Expand viewCollapse view
$VBoxManage list vms
"linuxserver" {2fc0dbb0-b151-4bee-83a7-533756adab91}
nohup VBoxHeadless -s "2fc0dbb0-b151-4bee-83a7-533756adab91" &
Attachments
linuxserver-2019-10-08-11-28-34.log.zip
(17.22 KiB) Downloaded 12 times
froghui
 
Posts: 4
Joined: 6. Oct 2019, 17:10

Re: start new VM report NS_ERROR_FAILURE (0x80004005)

Postby bkoy » 8. Oct 2019, 08:08

Try using Terminal then use:

VirtualBoxVM --startvm "VM Name"
bkoy
 
Posts: 1
Joined: 8. Oct 2019, 08:05

Re: start new VM report NS_ERROR_FAILURE (0x80004005)

Postby froghui » 8. Oct 2019, 10:12

Yes, It works.

Now the question is why we can not start vm from GUI? And I can not start VM from vagrant, either.
froghui
 
Posts: 4
Joined: 6. Oct 2019, 17:10


Return to VirtualBox on Mac OS X Hosts

Who is online

Users browsing this forum: No registered users and 20 guests