Problem getting VirtualBox to run

[tregarth]

Hi. First time poster to this forum, but I have run VirtualBox in the past, though not in quite some time (more than a year).

My setup:

I am running on a 17-inch, MacBook Pro, Mid-2009 with a 2.8 Ghz Intel Core 2 Duo Processor and 4 GB 1067 Mhz DDR3 Memory. My graphics card is an NVIDIA GeForce 9400 256 MB. and I am running OS X 10.8.5.

I am trying to run VirtualBox 5.0.6, but I have tried several different versions with the same error message. The message is as follows:

Failed to create the VirtualBoxClient COM object.

The application will now terminate.

Callee RC: NS_BASE_STREAM_WOULD_BLOCK (0x80470007)

I have already looked in the forums for this message, as well as doing a search.

I was able to find the "Failed to create the VirtualBoxClient COM object." portion of the error message, but the "Callee RC:" was different.

Any ideas?

[socratis]

Searching for "NS_BASE_STREAM_WOULD_BLOCK site:forums.virtualbox.org" returns several results. Most of the problems are due to wrong permissions in the filesystem.

• Uninstall VirtualBox with the "VirtualBox_Uninstall.tool".
• Repair Permissions from within the Disk Utility (Applications/Utilities).
• Re-install VirtualBox.
• Post the output of the command:

  ls -al /Applications/VirtualBox.app/

[tregarth]

Thanks for the reply. I thought that I had done a search for "NS_BASE_STREAM_WOULD_BLOCK" and found no results. So, I did the search again and looked at the results, but I don't see that any of them apply.

I followed your advice.
   • I Uninstalled VirtualBox with the "VirtualBox_Uninstall.tool"
   • I Repaired Permissions from within the Disk Utility (Applications/Utilities).
   • I Re-installed VirtualBox.
   • Below is the post of the output of the command:
      ls -al /Applications/VirtualBox.app/

drwxr-xr-x    3 root  admin   102 Oct 16 03:01 .
drwxrwxr-x+ 146 root  admin  4964 Oct 16 22:54 ..
drwxr-xr-x    8 root  admin   272 Oct  2 07:58 Contents

I have tried running VirtualBox again, but I received the same error message. I even tried repairing the permissions again from within Disk Utility after re-installing VirtualBox, but once more received the identical error message.

Edited:
ls -al /Applicaations/VirtualBox.app to make it correct (although I think I had pasted the command from your post the first time) and ran it again with the correct command as shown above. This gave the new results shown in the (edited) quote above.

[socratis]

Permissions seem to be alright. Is there anything out of the ordinary that you may have done to your host? Think hard... For example, did you do a fresh install of 10.8.x or an upgrade (which may or may not carry issues from the past).

[tregarth]

Thanks for the reply.

I did an upgrade when I installed 10.8. Unfortunately, I have probably done a number of other things as well (enough that I'm not certain that I can remember them).

I am somewhat of an experimenter, alway pushing the envelope of what my current computer is capable of doing, although my computer is usually several hardware versions behind the current model.

I also had allowed my hard drive to get within 1 or 2 GB of totally full. I have cleared much of it out now, and have 144 GB available.

I have tried several Emulators in the past, including iEmulator, Q, Winebottler, Wineskin, Virtual PC, and PlayOnMac, as well as VirtualBox. I have had a couple of successes, but many failures, and some of these no longer seem to run under Mac OS 10.8.

I'm sorry I can't give you more information, but that is what I can remember at present. I've been using Macs since late 1984, the year the first Mac came out.

[socratis]

I have probably done a number of other things as well (enough that I'm not certain that I can remember them)... I am somewhat of an experimenter ... I also had allowed my hard drive to get within 1 or 2 GB of totally full ... I have tried several Emulators in the past and some of these no longer seem to run under Mac OS 10.8.

Based on the above quotes, I'm pretty sure that I, and (I'm willing to bet) no one can tell what's actually going on with your system. Not even Apple itself! I bet (again) that if you go to an Apple genius bar, they'll tell you to reformat and start anew. Which would be my advice as well.

I've been using Macs since late 1984, the year the first Mac came out.

GREAT! But, since you're an old-timer, there are some things that have changed in the last 30 years, and I don't mean that in any derogatory way. Back in the 80's PCs were a single-user system, no permissions, no users, no nothing. For example, are you running every day as a simple user or as an administrator? That can make THE difference between a running system and a broken one.

[tregarth]

Thanks for the reply.

Based on the above quotes, I'm pretty sure that I, and (I'm willing to bet) no one can tell what's actually going on with your system. Not even Apple itself! I bet (again) that if you go to an Apple genius bar, they'll tell you to reformat and start anew. Which would be my advice as well.

I may eventually try that, but I'm trying to solve the problem without reformatting first.

GREAT! But, since you're an old-timer, there are some things that have changed in the last 30 years, and I don't mean that in any derogatory way. Back in the 80's PCs were a single-user system, no permissions, no users, no nothing. For example, are you running every day as a simple user or as an administrator? That can make THE difference between a running system and a broken one.

According to advice I've seen in different sources over the years, I have two accounts set up on my computer, one to use to administer the computer as a whole which I created first and almost never use, and one for everyday operations, although I have given both admin rights. Since you mentioned this (and while I was in the process of writing this post), I switched to the other account and tried running VirtualBox there. It ran. Therefore, I must have done something to my everyday account which is different. As you say, I may have to recreate this account to make things work. Let me think and try a few things first, though.

Thanks so much for your help, and if you have any other ideas, please feel free to continue to suggest them!

[socratis]

I switched to the other account and tried running VirtualBox there. It ran.

Hmm.... That definitely shows some "corruption" on your everyday simple-user account (which, BTW, is what I'm doing myself). So, try to do the following as a first step.

Rename your "~/Library/VirtualBox" folder to something different, like "~/Library/VirtualBox-backup". Run VBox. You will have lost all of your VMs (in theory only, don't worry), but that should give you an idea where the main source of the problem might be.

If VBox runs, add a VM that gave you trouble in the past. Try to launch it. Report back. Oh, and BTW if you don't mind could you post a zipped VBox.log file from that VM?

[tregarth]

Since you suggested installing my system again, I was trying to get things stored on another hard disk preparatory to wiping everything out. In the process, I discovered that I still had Darwine installed, which supposedly no longer works on the new system, so I removed it. Then, I noticed your next reply which suggested:

Rename your "~/Library/VirtualBox" folder to something different, like "~/Library/VirtualBox-backup". Run VBox. You will have lost all of your VMs (in theory only, don't worry), but that should give you an idea where the main source of the problem might be.

I renamed the folder, then ran VBox. I worked.

I had no VMs because I had lost them since I had tried it in the past, so I made a new VM, and installed Windows in it. So far, it is working correctly.

Even though I don't have a log from any previous VMs from the past, would you still like me to post one from where I was trying to get VBox to run unsuccessfully?

Thanks so much for the help!

[socratis]

Sorry for the late reply. If your new VM run successfully then there's no problem. Or to be more precise, there shouldn't be a problem.

What you need to do now is to "Add..." back your previous VMs. Go to menu Machine, Add. Locate your previous VMs and choose the .vbox file for each one of them and add them back.

[ansisys]

I've got the same problem as above…tried everything I believe..
reinstall of the virtual box, changing access rights, groups, reinstalling extension pack, checking permission and repairing these with disk tools, renaming VirtualBox folder, installing it new... and what not - the result is always the same - vms won't start. WTF??? Few days ago it was still running fine.

Failed to load R0 module /Applications/VirtualBox.app/Contents/MacOS/VMMR0.r0: World writable: '/Applications' (VERR_SUPLIB_WORLD_WRITABLE).
Failed to load VMMR0.r0 (VERR_SUPLIB_WORLD_WRITABLE).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

ls -al /Applications/VirtualBox.app/
total 0
drwxr-xr-x   3 root  admin   102 Nov  4 03:25 .
drwxrwxrwx+ 57 root  admin  1938 Nov  4 03:25 ..
drwxr-xr-x   8 root  admin   272 Oct 15 16:20 Contents

Anyone has an idea, what else can be done, yet?

Code: Select all

ls -al /Applications/VirtualBox.app/Contents/MacOS/
total 265368
drwxr-xr-x  66 root  admin      2244 Oct 15 16:20 .
drwxr-xr-x   8 root  admin       272 Oct 15 16:20 ..
-rw-r--r--   1 root  admin     62848 Oct 15 16:20 DbgPlugInDiggers.dylib
-rw-r--r--@  1 root  admin   3468626 Oct 15 16:19 UserManual.pdf
-rw-r--r--   1 root  admin     28000 Oct 15 16:20 VBoxAuth.dylib
-rw-r--r--   1 root  admin     52096 Oct 15 16:20 VBoxAuthSimple.dylib
-rwxr-xr-x   1 root  admin    139600 Oct 15 16:20 VBoxAutostart
-rwxr-xr-x@  1 root  admin      2046 Oct 15 16:19 VBoxAutostartDarwin.sh
-rwxr-xr-x   1 root  admin    195392 Oct 15 16:20 VBoxBalloonCtrl
-rw-r--r--   1 root  admin   2670576 Oct 15 16:20 VBoxDD.dylib
-rw-r--r--   1 root  admin    210240 Oct 15 16:20 VBoxDD2.dylib
-rw-r--r--@  1 root  admin     19104 Oct 15 16:19 VBoxDD2R0.r0
-rw-r--r--@  1 root  admin    222146 Oct 15 16:19 VBoxDDR0.r0
-rw-r--r--   1 root  admin    385360 Oct 15 16:20 VBoxDDU.dylib
-rwxr-xr-x   1 root  admin     23488 Oct 15 16:20 VBoxDTrace
-rw-r--r--   1 root  admin    133040 Oct 15 16:20 VBoxDbg.dylib
-rw-r--r--   1 root  admin     44832 Oct 15 16:20 VBoxDragAndDropSvc.dylib
-rw-r--r--@  1 root  admin   1048576 Oct 15 16:19 VBoxEFI32.fd
-rw-r--r--@  1 root  admin   1048576 Oct 15 16:19 VBoxEFI64.fd
-rwxr-xr-x   1 root  admin     79536 Oct 15 16:20 VBoxExtPackHelperApp
-rw-r--r--@  1 root  admin  58992640 Oct 15 16:19 VBoxGuestAdditions.iso
-rw-r--r--   1 root  admin     40944 Oct 15 16:20 VBoxGuestControlSvc.dylib
-rw-r--r--   1 root  admin     54160 Oct 15 16:20 VBoxGuestPropSvc.dylib
-rwsr-xr-x   1 root  admin     49200 Oct 15 16:20 VBoxHeadless
-rw-r--r--   1 root  admin    138816 Oct 15 16:20 VBoxHeadless.dylib
-rw-r--r--   1 root  admin     35216 Oct 15 16:20 VBoxHostChannel.dylib
-rwxr-xr-x   1 root  admin   1313120 Oct 15 16:20 VBoxManage
-rwsr-xr-x   1 root  admin     27792 Oct 15 16:20 VBoxNetAdpCtl
-rwsr-xr-x   1 root  admin     49200 Oct 15 16:20 VBoxNetDHCP
-rw-r--r--   1 root  admin    181152 Oct 15 16:20 VBoxNetDHCP.dylib
-rwsr-xr-x   1 root  admin     49200 Oct 15 16:20 VBoxNetNAT
-rw-r--r--   1 root  admin    306016 Oct 15 16:20 VBoxNetNAT.dylib
-rw-r--r--   1 root  admin    210000 Oct 15 16:20 VBoxOGLhostcrutil.dylib
-rw-r--r--   1 root  admin    146144 Oct 15 16:20 VBoxOGLhosterrorspu.dylib
-rw-r--r--   1 root  admin    195040 Oct 15 16:20 VBoxOGLrenderspu.dylib
-rw-r--r--   1 root  admin    244928 Oct 15 16:20 VBoxPython2_6.so
-rw-r--r--   1 root  admin    249232 Oct 15 16:20 VBoxPython2_7.so
-rw-r--r--   1 root  admin    601392 Oct 15 16:20 VBoxREM.dylib
-rw-r--r--   1 root  admin   4990640 Oct 15 16:20 VBoxRT.dylib
-rwxr-xr-x   1 root  admin   5756368 Oct 15 16:20 VBoxSVC
-rw-r--r--   1 root  admin    239632 Oct 15 16:20 VBoxSVGA3D.dylib
-rw-r--r--   1 root  admin     45280 Oct 15 16:20 VBoxSVGA3DObjC.dylib
-rw-r--r--   1 root  admin     45824 Oct 15 16:20 VBoxSharedClipboard.dylib
-rw-r--r--   1 root  admin   1128256 Oct 15 16:20 VBoxSharedCrOpenGL.dylib
-rw-r--r--   1 root  admin     59632 Oct 15 16:20 VBoxSharedFolders.dylib
-rw-r--r--   1 root  admin   2537808 Oct 15 16:20 VBoxVMM.dylib
-rw-r--r--   1 root  admin   1023696 Oct 15 16:20 VBoxXPCOM.dylib
-rw-r--r--   1 root  admin     78176 Oct 15 16:20 VBoxXPCOMC.dylib
-rwxr-xr-x   1 root  admin     50256 Oct 15 16:20 VBoxXPCOMIPCD
-rw-r--r--@  1 root  admin   1742840 Oct 15 16:19 VMMR0.r0
-rwsr-xr-x   1 root  admin     49248 Oct 15 16:20 VirtualBox
-rw-r--r--   1 root  admin   9952864 Oct 15 16:20 VirtualBox.dylib
-rwsr-xr-x   1 root  admin     49200 Oct 15 16:20 VirtualBoxVM
drwxr-xr-x   3 root  admin       102 Oct 15 16:19 accessible
drwxr-xr-x   7 root  admin       238 Oct 15 16:19 components
drwxr-xr-x   5 root  admin       170 Oct 15 16:19 dtrace
-rw-r--r--   1 root  admin    171232 Oct 15 16:20 libvboxjxpcom.jnilib
drwxr-xr-x  46 root  admin      1564 Oct 15 16:19 nls
-rw-r--r--@  1 root  admin       542 Oct 15 16:19 org.virtualbox.vboxautostart.plist
-rw-r--r--@  1 root  admin       423 Oct 15 16:19 org.virtualbox.vboxballoonctrl.plist
-rw-r--r--@  1 root  admin       677 Oct 15 16:19 org.virtualbox.vboxwebsrv.plist
drwxr-xr-x   4 root  admin       136 Oct 15 16:19 sdk
-rwxr-xr-x   1 root  admin   2202352 Oct 15 16:20 vbox-img
-rwxr-xr-x@  1 root  admin    121259 Oct 15 16:19 vboxshell.py
-rwxr-xr-x   1 root  admin  32755040 Oct 15 16:20 vboxwebsrv
-rwxr-xr-x   1 root  admin     32096 Oct 15 16:20 vmstarter

What I'm missing here?

[Martin]

You didn't repair the relevant folder permissions:

Failed to load R0 module /Applications/VirtualBox.app/Contents/MacOS/VMMR0.r0: World writable: '/Applications' (VERR_SUPLIB_WORLD_WRITABLE).

ls -al /Applications/VirtualBox.app/
total 0
drwxr-xr-x 3 root admin 102 Nov 4 03:25 .
drwxrwxrwx+ 57 root admin 1938 Nov 4 03:25 ..

[ansisys]

You didn't repair the relevant folder permissions

Yep. That's it.

Code: Select all

sudo chmod -R 755 /Applications/

did the job. Thanks a lot. The question is, what could have changed the rights in this folder. I've red somewhere that it could be the flash update, but that's not, what I was doing recently.

Anyway, this part is done. I'm grateful for that hint mate, I'm indeed. Issue solved…

[Juta]

Hello,

I have installed VirtualBox-5.0.16-105871-OSX on my MacBook Pro late 2008 which have installed OS X El Caitan 10.11.6.

I've created new VM and try to install Windows 7 via iso file. bur when I try to start I receive this error message:

Apertura di una sessione per la Macchina Virtuale Windows 7 non riuscita.

Failed to load R0 module /Applications/VirtualBox.app/Contents/MacOS/VMMR0.r0: World writable: '/Applications' (VERR_SUPLIB_WORLD_WRITABLE).

Failed to load VMMR0.r0 (VERR_SUPLIB_WORLD_WRITABLE).

Codice 'uscita: NS_ERROR_FAILURE (0x80004005)
Componente: ConsoleWrap
Interfaccia: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Could anyone help me to resolve this issue?

Regards,
Juta

[socratis]

'Juta'
The answer/solution is literally above your post, which part don't you understand? I could help you figure it out...