Page 2 of 2
Re: OSX 10.10 Yosemite
Posted: 15. Nov 2014, 02:04
by loukingjr
Sorry, I don't read German but,
1. Did you run repair disk permissions?
2. Do you have an anti-virus program installed?
Re: OSX 10.10 Yosemite
Posted: 15. Nov 2014, 02:42
by michaln
Before there's more crazy speculation... /Users/vbox/tinderbox/4.3-mac-rel/src/VBox/Main/src-server/VirtualBoxImpl.cpp refers to a path/file on the system which built the OS X VirtualBox release. There was user 'vbox' on that machine and 'Tinderbox' is the software which runs the builds. Ignore the path. It has nothing to do with the system on which the error occurred, it is simply pointing to the exact source file where the error was detected.
Does the settings file really have version '1.2-macosx' (as opposed to '1.12-macosx')? If so, what was the previous VirtualBox version installed on the system? It is possible (but I am speculating) that the current VirtualBox version doesn't handle every possible outdated settings version. Normal users upgrade every once in a while and never run into this problem.
Re: OSX 10.10 Yosemite
Posted: 15. Nov 2014, 03:04
by loukingjr
michaln wrote:Before there's more crazy speculation... /Users/vbox/tinderbox/4.3-mac-rel/src/VBox/Main/src-server/VirtualBoxImpl.cpp refers to a path/file on the system which built the OS X VirtualBox release. There was user 'vbox' on that machine and 'Tinderbox' is the software which runs the builds. Ignore the path. It has nothing to do with the system on which the error occurred, it is simply pointing to the exact source file where the error was detected.
Does the settings file really have version '1.2-macosx' (as opposed to '1.12-macosx')? If so, what was the previous VirtualBox version installed on the system? It is possible (but I am speculating) that the current VirtualBox version doesn't handle every possible outdated settings version. Normal users upgrade every once in a while and never run into this problem.
"crazy speculation" might be a bit extreme michaln but thank you for the clarification.
because the OP started the thread stating…
I am new in the VirtualBox world and faced the first problems.
System: iMac Intel Based (end 2009) Core i7, OSX 10.10 Yosemite German
What I have done: I´ve donloaded VirtualBox-4.3.18-96516-OSX, installed it.
I was under the impression 4.3.18 was the first version installed. Of course I could be wrong. It happens.

Re: OSX 10.10 Yosemite
Posted: 15. Nov 2014, 13:09
by loukingjr
@DaniOSX Try running the VirtualBox_Uninstall.tool. If you didn't save it to your disk it would be in the VirtualBox .dmg file. Then try installing VirtualBox again.
Re: OSX 10.10 Yosemite
Posted: 15. Nov 2014, 18:33
by DaniOSX
Hey guys
I tried several things.
1. No Anti Virus software were running, I uninstalled all anti virus software
2. ran the permission permission in HD utility
3. uninstalles Vbox with script in the dmg.
4. restarted my Mac
5. Installed Vbox 4.3.18 again
6. Open VirtualBox
7. Same error.... =(
To answer one of your questions:
Vbox 4.3.18 is the first version i try to install, after this fails, i tried 4.3.16 but same error.
For me it looks like that this version simply not work for OS X 10.10
I am really sad but i think I have to try another tool instead of Vbox.
But anyway, thank you guys for helping me.
Cheers
Daniel
Re: OSX 10.10 Yosemite
Posted: 15. Nov 2014, 18:46
by loukingjr
Sorry it didn't work. VB 4.3.18 does work with OSX 10.10. I have them installed on 3 macs. Maybe someone will have another idea.
Re: OSX 10.10 Yosemite
Posted: 19. Nov 2014, 17:45
by Perryg
loukingjr wrote:michaln wrote:Before there's more crazy speculation... /Users/vbox/tinderbox/4.3-mac-rel/src/VBox/Main/src-server/VirtualBoxImpl.cpp refers to a path/file on the system which built the OS X VirtualBox release. There was user 'vbox' on that machine and 'Tinderbox' is the software which runs the builds. Ignore the path. It has nothing to do with the system on which the error occurred, it is simply pointing to the exact source file where the error was detected.
Does the settings file really have version '1.2-macosx' (as opposed to '1.12-macosx')? If so, what was the previous VirtualBox version installed on the system? It is possible (but I am speculating) that the current VirtualBox version doesn't handle every possible outdated settings version. Normal users upgrade every once in a while and never run into this problem.
"crazy speculation" might be a bit extreme michaln but thank you for the clarification.
because the OP started the thread stating…
I am new in the VirtualBox world and faced the first problems.
System: iMac Intel Based (end 2009) Core i7, OSX 10.10 Yosemite German
What I have done: I´ve donloaded VirtualBox-4.3.18-96516-OSX, installed it.
I was under the impression 4.3.18 was the first version installed. Of course I could be wrong. It happens.

Its alright Louis,
I believe michaln was referring to my post and not so much yours. But I have no idea why he even chimed in since he was not intending to actually help. In any case I stand by what I posted and as far as the normal user is concerned it is actual and correct. They would never see this folder structure had they not had an issue. The error message is at the least misleading and *is* hidden in the code and not where anyone other than ones that compile VBox would normally see it, nor would they understand why it posts an absolute value that does not exist on the end users machine.
Re: OSX 10.10 Yosemite
Posted: 19. Nov 2014, 18:03
by loukingjr
Perryg wrote:
Its alright Louis,
I believe michaln was referring to my post and not so much yours. But I have no idea why he even chimed in since he was not intending to actually help. In any case I stand by what I posted and as far as the normal user is concerned it is actual and correct. They would never see this folder structure had they not had an issue. The error message is at the least misleading and *is* hidden in the code and not where anyone other than ones that compile VBox would normally see it, nor would they understand why it posts an absolute value that does not exist on the end users machine.
I wasn't offended.
I was also wondering why he didn't propose a possible solution.
welcome back btw.
