Unable to open Virtualbox on Mac OS X

[sfigato60]

Hi,
I installed VirtualBox on my MacBook Pro but when I launch the application it does not open. In the console I get this message:

02/01/01 06:49:59 com.apple.launchd [1] (org.ntp.ntpd [174]) Stray process with pgid equal to this dead job: PID 178 PPID 1 ntpd

Supporting data:
OS: Mac OS X 10.5.8
Model Name: MacBook Pro
Processor Name: Intel Core 2 Duo
Processor Speed​​: 2.4 GHz
Memory: 2 GB

The version of VirtualBox is 4.1.8 for OS X hosts

I tried to uninstalling and reinstalling the program but without success.

Could someone help me?
thanks

[mpack]

You pm'd me for an answer to this, but I'm afraid that if I had an answer I would already have given it. In my experience this kind of problem is often a permissions problem, i.e. installing the software without full admin rights, but since I'm not a Mac user I could easily be wrong.

I did find one previous thread where a similar message popped up. Apparantly in your case "ntpd" is the process name? If so it doesn't ring any bells with me.

[rpmurray]

ntpd is the Network Time Protocol daemon and is not likely to have anything to do with his problem.

I suspect the fact that he appears to have only 2GB of ram on the host is the more likely culprit. It might be a good idea to open Activity Monitor and see how much RAM is left to run the VB application. mpack, your observation about a possible permissions problem also sounds like a likely scenario.

[sfigato60]

1) How do I install VB with full admin rights? (Please consider that I'm already administrator of my Mac)
2) The free memory system is 1,39GB.

Thanks

[rpmurray]

If you're the Admin of the Mac then if should install with full admin rights. Have you tried running the Repair Disk Permissions in the Disk Utility? If this is a permissions problem this will sometimes fix it.

[sfigato60]

I have launched the Repair Disk Permissions. I also tried to uninstall the Virtual box old version and install the new one (4.1.10 virtual box) but the result is the same, when I try to run VirtualBox it does not open (the multicolored circle of mac turns on for a few seconds and then disappears).
If I open the console into system library appears this message:

Mar 22 10:22:17 Macallister ReportCrash[413]: Formulating crash report for process VirtualBox[410]
Mar 22 10:22:17 Macallister ReportCrash[413]: Saved crashreport to /Library/Logs/CrashReporter/VirtualBox_2012-03-22-102215_Macallister.crash using uid: 0 gid: 0, euid: 0 egid: 0
Mar 22 10:22:17 Macallister com.apple.launchd[72] ([0x0-0x32032].org.virtualbox.app.VirtualBox[410]): Exited abnormally: Bus error

I tried to attach the file of the crash report but the system does not accept any type of file (I tried with .doc .pdf and .html, but always appear the message: "The extension ......is not allowed). Could you tell me how to send you this file? for me is pure Arabic.

If you help me I will be grateful.

[rpmurray]

I tried to attach the file of the crash report but the system does not accept any type of file (I tried with .doc .pdf and .html, but always appear the message: "The extension ......is not allowed). Could you tell me how to send you this file? for me is pure Arabic.

How about .txt? And you might try zipping it before you attach it.

[sfigato60]

Ok the extension .txt has been accepted. See file attached.
Thanks

[sfigato60]

Hi rpmurray,

have you seen my crash report?

[rpmurray]

have you seen my crash report?

Sorry, the people I work for had me busy doing some actual work.

I've taken a look and I don't see anything obvious other than VB is apparently having a problem with memory. Based on your posts and the file you attached it looks like you've been trying to install 4.1.8 and 4.1.10. I've seen other posts from users having trouble with the 4.1.x releases. Have you considered trying to install one of the 4.0.x releases to see it things work with that? If so then this could be a bug in the newer VB releases.

[sfigato60]

I tried to install both the version 4.0.16 to 4.0.2. The result is not changed. Attached you can find crash report for the version 4.0.2
Other suggestions?

[rpmurray]

The 4.0.x releases should work (I'm using 4.0.10) I can only assume that there's something on your MacBook Pro that is getting in the way of the VirtualBox app.

Take a look in the {hard drive]/Library/Extensions folder and see if the four VBox kexts are there. They're named VBoxDrv.kext, VBoxNetAdp.kext, VBoxNetFlt.kext, and VBoxUSB.kext. I'm just shooting in the dark but based on other posts in these forums errors would occur if any of these was not installed. While I think you'd probably get some kind of error message if any were not there it would be a step forward to rule this out.

The next thing you could try is create another Administrator user account and try to install VB in that account to see if it'll work. If it does then we know that something you have installed in the original account is causing the problem.

[sfigato60]

Under: /system/library/Extensions there was no file Vbox*.txt. So I followed these logical steps:
1) Cancelled Vbox 4.0.2
2) Created a new account with administrator privileges
3) Downloads VB version 4.0.10
4) Launched the program that works ....... miracle, you're great.

For your information after have installed VB I went to check if there were the extensions folder kexts, but in any case I did not find them.

Wanting to delete the new account I ask you some information (I hope the latest for you):
1) Which files do I copy from the new account to old?
2) In which destination folder, of old account, should I copy them?

Thanks

[rpmurray]

Under: /system/library/Extensions there was no file Vbox*.txt.

Ah, no. The kext files would be in /Library/Extensions, not in /System/Library/Extensions.

I don't think moving files from the new account to the old account would fix things. Assuming that the kexts are where they belong in /Library/Extensions in the old account it would mean that there is some other program or driver in the old account that is keeping VB from working and tracking down whatever that is is not going to be easy.

[sfigato60]

So you suggest leave things as they are and manage two accounts?